I also have this issue. I'm hoping it's a bug that the SwiftData team is planning to fix before release. If not, hopefully Apple releases some guidance for how to resolve this error. In the meantime, I'm ignoring it and hoping for the best.