“build disappears”

The app will indeed be relaunched using Region Monitoring even if force quit. Reliability problems usually occur if the region around the station is not suitably set. There are a number of reasons, and some misplaced expectations on how region monitoring works that could be causing this: the region could not be placed correctly. A common issue is to use coordinates from a map or obtained otherwise. As region monitoring is based on WiFi and mobile signals, and those are affected by attenuation and reflections, as far as region monitoring goes, exact coordinates from a map may not be in the correct position. So, if you are having an issue with a certain location, you may want to double check that you see yourself located at the correct place and get the center coordinates according to live location rather than using a map or otherwise obtained coordinates. the region could be too small. Depending on the environment, the minimum radius could vary between 100 to 500 meters (and sometimes more, in rural areas). If

I like galad87’s take on this. Rather than worrying about other folks’ apps, I suggest that you on your own products. And in that case the messaging is super clear: If your build system or final software depends on Rosetta, you should be working to break that dependency as a matter of priority. And if you have technical questions about how to do that, please post them here on the forums. We’re hear to help. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I have the same, across all applications. All builds were expired, one during initial review phase. I can't add any build to testflight and only get There was an error processing your request. Please try again later.

I have a similar problem. The app has even been distributed. I am trying to update the app with a new build. I have applied for expedited request and contacted apple support but no update. It has been stuck on waiting for review for over 2 weeks now.

Our app Miiro (App ID: 6759159052) was rejected for Guideline 3.1.2(c) on March 13. What is Guideline 3.1.2(c) about? Nobody remembers all those numbers and corresponding meanings in heart. The build moved to In Review shortly after but has been stuck there for over 29 hours with no status change. So what's the issue? You don't have to wait for your turn because you pay a subscription fee?

Same query here. I've tried everything I can think of to get the terms link to render content based on App Store Connect configuration. I can only get it working in local development in Xcode builds by passing a dedicated url to the supposedly custom terms link field, which, according to both common sense and official developer documentation, isn't necessary. I've set the policy link there, which works, but the terms link never renders the proper content, despite having opted into the standard EULA.