I generated a new archive and instead of using the organizer to upload the .ipa file, I exported it and used the transporter to successfully upload it. But it's still failing the processing phase and sending me an email about using private API's listed in it, which are not really listed at all.
Looks like I have to wait until all app store connect issues are resolved. If there is a private api being called, I'm hoping that once the App store connect issues are resolved on Apple's side, I will finally get the list of private Apple APIs that are being used by my app or some pod
BloxHead
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
Post
Replies
Boosts
Views
Activity
Other reasons why I think the issue is with App Store Connect is if I use the "Validate App" button the app successfully passes.
Update: Still getting this issue no matter what I try to do. I'm now wondering if it's really an issue in my app or if it's app store connect that is problematic. A quick look at system_status reveals that App Store Connect is having App Upload and App Processing Issues. I'll wait until that goes back to normal before submitting again
You can't unless you get a job @apple to make the compiler changes.
What does this have to do with my question?
If the order of lifecycle calls when the app is run directly on an iPhone is the one and true way, how can I force Xcode to use the same lifecycle sequence, so i can debug this issue? Thanks