Failing for me - the .ipa won't generate
Post
Replies
Boosts
Views
Activity
Same here - seeing "Sorry, something went wrong. Try your request again. If the problem continues"
I can build and submit but cannot do anything within app store connect, keep seeing Sorry, something went wrong. Try your request again. If the problem continues contact us
If I try and add release notes or change logs or anything else, I see An error has occurred. Try again later.
What's annoying is that https://developer.apple.com/system-status/ does not acknowledge it. It's misleading and confusing as I've reset our wifi / network connection dozens of times thinking it must be me.
I've submitted a proposal here: https://developer.apple.com/forums/thread/705799#705799021
This, my friend, is why there's an ongoing multi-million dollar litigation with Epic vs Apple. No you cannot.
It's now been several hours (around 4 hours from the time I started counting) and the status page still shows that everything's okay. Yet, everything is NOT okay. We've been unable to process and submit our builds to App Store / Testflight.
Just answering your original question - Core data is not the right choice for this at all.
See this:
https://developer.apple.com/forums/thread/705825
https://developer.apple.com/forums/thread/705799
And that's my point. If you click on one of them, they show you that the performance issues began roughly 2 hours ago. That's incorrect - if you scan through the forums, it's been at least 8 hours this way. Why have a status page if it's updated manually, and that too after several hours of reporting and then misreport the incident time?
It's starting to look like this: https://github.blog/2022-03-23-an-update-on-recent-service-disruptions/
You just have to use a slightly different App Icon (use a different color for Admins). Green for Users and Blue for Admins for example.
Take a break, sip some tea, go out for a walk and come back and try later. Since this is the new norm, their servers seem to be okay at midnight (NY time). Try and submit builds then.
Here we go again.
It seems to be caused by enabling ENABLE_USER_SCRIPT_SANDBOXING. It was working fine in Xcode 14 beta 1 and 2 though. The Input Files and Output Files have been correctly specified though, yet it seems to be failing.