@DTS Engineer Hi Ziqiao, could you provide more insights and updates if you have any? Thanks!

@Daniel Scheibe Thanks for sharing your solution. This workaround doesn't seem quite convenient because we need to revert the permission back when creating a new model version. :(( Also, if you could provide more information, when did you first find out this issue and how long it's been around for you?

That's interesting. I created this model in Version 16.3 (16E140), which I believe is the current stable XCode release. I created new models using Editor > Add Model Version.... I just tested creating another model, and the new one still contains usedWithSwiftData="YES". I don't need my models to be SwiftData compatible at this moment. So, do you think removing this field would resolve the issue?

Hi Ziqiao, Thanks for help me out. I tried to create a new project and indeed there is no issue. I tried to move my model that has the issue to the new project and the issue persist. So your speculation of my .xcdatamodeld being weird is correct. You can find my project that reproduces the issue here: https://drive.google.com/file/d/1nHYsl9JANR9YI4jpXA98wDWp28BGQh50/view?usp=sharing. Before opening the project, you can see that coredataissue/Model.xcdatamodeld/.xccurrentversion is GroupMetaData.xcdatamodel, but after opening the xcode project, the coredataissue/Model.xcdatamodeld/.xccurrentversion becomes Model.xcdatamodel.

Editor > Canvas > Use Legacy Previews Execution Works for me. Thanks!