Hey @JordanBettridge, No problem at all! The length of time in which your application is in review is going to be massively subjective! In general, Apple is pretty good when you have a "simple" application. What I mean by simple is no in-app payments and very few entitlements. These submissions are going to take the least amount of time and a 2-6 day turn around could be accounted for. As soon as you start to including things like in-app payments, background audio, bluetooth, HealthKit, or pretty much anything that requests access to or gets access to more user information is going to trigger a longer App Review window. If you have an application like this and are expected to communicate a turn around time for a project schedule, I would suggest 3-5 weeks. Almost a guarantee that Apple will ask for videos, documentation and clarifying questions as to why your application needs the information if it is not abundantly clear to the user in the application. Even if it is, they will still ask for it. The Apple Developer Program for an Individual and an Organization both cost $100 USD annually. There is an Apple Developer Program type called "Enterprise" which is $300 USD annually. For the situation you have described an Enterprise Apple Developer Program account would not help, but I wanted to make sure I acknowledged its existence. As you first get going with App Store submissions, I would plan on being rejected 2-3 times which is normal. You will learn TONS about how to work with Apple. Many times it will feel like they are a wall, but if you step away and come back and look at it from the lens of they are trying to protect your family members from a scam application, most of the time their rejections and questions for more information will make sense. I would say no matter what, our organization always has a 2-week lead time for the App Review process and then if Apple approves faster we count it as a success story. Hopefully this helps!

Hey @robnotyou, Great solution! I was thinking the same thing myself. Much more reliable to let an Apple service do the heavy lifting that way the user has the same experience across the device with Apple services and not have a personal application say there is no network activity when the rest of the device is working.

Hey @limengke, Thanks for pointing this out! It looks like this is now working for me as well! I am still having an issue with the `Read the App Store Version Information on a Build" API, but it is great that this API is now back to working like normal! Great catch on this!

Thanks @Developer Tools Engineer for posting this! This is great and I have not seen it yet!

No problem at all! When I first started using the API I didn't care about the response headers and now I watch them extremely carefully. Watching the headers is a good way of detecting when Apple is making changes that they do not announce.

Hey @huanling820713, Would it be possible for you to run the command as below and let us know if that gives you anything additional? codesign -fs FS --timestamp --force --deep --verbose --options runtime --entitlements ENTITLEMENTS TOOL_NAME Happy coding!