Sorry, I'm getting to the discovery that it is because I didn't respect the .safeArea(cornerAdaptation: .vertical) guide. Only upside down folded remains a mystery and still eats the touches at the top.

In our case it was resolved by submitting a new binary with the relevant review note and it was approved promptly. We don't know what would happen if we would not resubmit and just waited for the Apple Review response on the crash logs request.

Yes, it has been resolved, thank you!

I have a very similar issue with being rejected for the app crash with in review and rejection emails being sent by Apple in the same second and no crash log or device information is provided in the rejection message in the App Store Connect: https://developer.apple.com/forums/thread/825318

Thank you for the reply and extended info! Part of the effort was to see how/if -disable-dynamic-actor-isolation works. After a day of testing I'd say it really works for iOS targets and not working for me for the watch target, there is a chance I'm applying the flag wrong. I updated the watch target now to count with the dynamic concurrency checks. I wonder when/if staying on swift 5 will become "penalized" by facing obstacles when new swift and xcode versions come.

Actually reading more of the act, it says in Article 22 p.4 and p.5 that provided personal information can't be shared publicly, if I understand it right. https://digitalservicesact.cc/dsa/art22.html "for purposes relating to his or her trade, business, craft or profession." makes every dev with app in the App Store a EU DSA trader, if the app is offered in EU? I think EU DSA goes after traceability of "content", not money.

Had the same problem with Xcode 14.3 and this solution helped. Thanks! A bit of patience required to wait until Xcode fully indexes the source, but after that auto-complete seems to work again.

One would expect changes like this to be announced at WWDC so we all have time to prepare and provide feedback. And Apple would have time to update the documentation :). I wonder what/why was the urgency in this case.

+1 to your karma. Still the issue in iOS 16.3 and this is still the solution. Thank you.

I tried to build and submit a different target from the same project, the one that doesn't have an Apple Watch Extension and there are no warnings from the App Store Connect for this one. Looks like these warnings might be connected to the Apple Watch Extensions.

Wait, it can be a good sign? So AppStore might be already offering the fixed version? I'm looking at mine UPDATE in the AppStore and can't figure out which version it will be installing, shame. So 13C90 gives that error when installed via AppStore and doesn't give it when installed via dev downloads? These might be still different builds, even if numbered the same - that already happened previously, to perfect the chaos.