I worked on this by preparing a version of my application that was good enough to be approved by Apple, although that was not where I wanted it to be for the first release. I sent it just before 180 days, but set a future release date on the Rights and Prices tab in iTunes Connect. Apple approved the binary, and I continued to work on the application without any additional warnings about expiration. I was even able to move the release date further into the future to give myself more time.
I donāt know what would happen if my expression were rejected by Apple or I myself rejected it. It might have been nice, but I preferred playing it safe and imagining something that met all the review recommendations.
Now I'm still not ready for a public release, but I'm ready for beta testing. I submitted my latest version for review, and Apple also approved it. At the moment, although the application is still not publicly available, I can create promo codes and give them to beta testers, and they can download the application from the App Store using promo codes. In my case, this is better than using over 100 devices available in my developer account. The trade-off is that every beta I want to share has to go through the Apple review process.
In any case, setting a release date in the future will allow you to meet the 180-day download period without releasing anything before you are ready. When you are ready to release, you can send your final version, make sure it is approved, and then transfer the release date to the desired date.
arlomedia
source share