I started to receive this warning because Firebase was getting initialized before my SKPaymentQueue delegate

My question requires an interpretation of the language in 5.1.1 (iv) because I will be using the Google UMP to collect UE GDPR for my ads that are served from AdMob. Non-UE users will still default to Apple's ATT. Effective in January 2024, if GDPR consent is not fully granted, or if it is not specifically configured using "Manage Options" in such a way as to allow AdMob to serve ads, no ads will be delivered from AdMob. The user-interface from the Google framework is so complicated and convoluted that it will be virtually impossible for a user to define the correct "configuration" - even if they want to. That being the case, any selection other than "Consent" will effectively disable ads from AdMob; thus preventing developers (who rely on AdMob) from generating ad revenue when GDPR applies. My question is whether it is acceptable under 5.1.1 (iv) for me to restrict access to my app unless the user provides the necessary consent to meet AdMob's requirements? Would restricting the app to a "limited evaluation" be considered "forcing the user to consent to unnecessary data access"? Google has indicated that I have the right to restrict my app in the Play Store, but I need a "judge's ruling" for the App Store. Thank you!

One feature of my app is consistently crashing on 16.3.1 and the crash manifests as a device "reset" so there are no logs or crash reports. A simulator would be extremely valuable for cases like this. Everything appears to be good on 16.4 and 15.5. I don't want to attach the device to Xcode because I try to use it solely for TestFlight installs in order to ensure that foundational updates to the app are sequentially installed and tested. In all likelihood, I'll have to upgrade the o/s earlier than I would like, in order to confirm that the issue is specific 16.3.1 and not to the device itself. I hate not identifying a root cause because it's almost guaranteed that the issue will raise it's head again in the future and potentially be even more critical.

I'm getting this error message, too, but it appears to be benign. How awesome would it be if the folks who make the changes to XCode ALSO wrote some apps?

Bueller? Bueller? No updates after 2 weeks? Issue still exists.

This sounds like great news to me! But to be clear the I completely understand you: I should disable bitcode in my app (I’ve seen guidance on that). Then, the local dsym files can be used with Crashlytics?

metehandemircioglu's solution worked for me as well.

Same Issue. Checked the Apple Systems Availability and everything is green...huh?