I can confirm it's also working for me in beta 5.

Thanks for this. I was having the same problem.

Your code is non-standard because you embed a ModelObject (ItemDetail) inside another ModelObject (Item) without defining a relationship. Don’t do that. You need to either make ItemDetail a plain struct, or make it a @Model with a relationship defined between the two. I’ve never seen any Swift Data code that does what you do here. If you don’t wan to link the deletion, you can use deleteRule: .nullify instead.

Thank you for the reply. Last night I requested a phone call via App Store Connect and the reviewers confirmed that I am scheduled to receive a phone call to discuss how we can resolve the issue. I don’t want you to start a second process with App Review on my account since I’m sure we can figure it out with the planned phone call.

I had a customer email me over night that the error had gone away for them as well. I'll be reaching out to other affected customers but I'm cautiously hopeful. I've been working furiously to set up a API proxy server to route calls from the app through (thereby using the REST API on my server, and potentially getting rid of WeatherKit entirely). I still think I want to finish that work so I can have some insurance in case I need to suddenly switch weather providers.