This is still an issue with iOS16 Beta 4

I did some more digging and determined that the issue is the use of a Button within the ForEach loop. I had a response from Apple, where they acknowledged the issue and are investigating. There doesn't appear to be any timeline for resolution. They did suggest that a workaround would be to replace the Button with an .onTapGesture. This worked for me.

An update. Looks like Apple changed something behind the WeatherQuery hourly(startDate: endDate:) method ( Documentation Link ). My code set up a date range a little over 10 days in duration as at original implementation time it ensured the maximum hourly weather entries were returned  let forecast = try await self.service.weather(for: location, including: .hourly(startDate: startDate, endDate: endDate)) The call stopped generating the error if I ensured that the duration was no more than 10 days so it seems that Apple has started enforcing a maximum data range to return. I've not seen anything in the documentation warning about this.....

After a lot of digging I finally found a solution that worked - at least for me. Seems that somehow something had become corrupt in the list of recent packages held in the Xcode preferences plist. I edited ~/Library/Preferences/com.apple.dt.Xcode.plist and deleted a bunch of of items from the IDESwiftPackageAdditionAssistantRecentlyUsedPackages key. After doing this, did the usual cache and derived data stuff and things started working again. Hope this helps someone else.

I'm seeing the same issue. My previous build worked with no warnings and my latest submitted build is receiving the warning with ASC reporting the app as no longer compatible...

I've opened a support call with Apple and have included a link to this thread to try to demonstrate it isn't just an individual problem. Upgrading to Xcode 16.1 RC hasn't made any difference, but as the issue seems to be something to do with some Apple post-processing on ASC I wasn't really expecting it to....

I never received a response from Apple, but it appears they've fixed the problem. Just successfully submitted a new build and all back to normal.