Hello,
We are preparing to submit our banking application to the App Store and would appreciate some guidance regarding our review and release process.
Due to our organization's deployment process, we plan to submit a production build that is configured to connect to our UAT backend during App Review. This will allow the App Review team to test all functionality using dedicated test credentials.
After the app is approved, we intend to submit another build that is identical in functionality but configured to connect to our production backend before releasing the app to customers.
A few questions:
- Is this approach acceptable under the App Store Review Guidelines?
- Has anyone successfully followed a similar workflow for enterprise or banking applications?
- Since the second submission would primarily change the backend environment (UAT → Production), is it generally reviewed as a normal update, or is there anything we should be aware of?
- Our planned public launch is 7 September 2026. Is there any recommended approach to help ensure the production update is reviewed before the launch date? We understand review times cannot be guaranteed.
- Due to our bank's security policy, our UAT environment is available only from 10:00 AM to 10:00 PM IST (Indian Standard Time). Is mentioning this in the App Review Notes sufficient, or is there a better way to communicate these testing hours to the App Review team?
The app will be fully functional during review, and we will provide complete test credentials and any other information required by the App Review team.
We appreciate any guidance or best practices from Apple or developers who have gone through a similar review process.
Thank you!