This question already has an answer here:<ul><li> <a href="/questions/14977624/how-to-debug-a-crashing-release-build" dir="ltr" rel="nofollow">How to debug a crashing release build? [duplicate]</a> <span class="question-originals-answer-count"> 2 answers </span> </li> </ul>
I constantly encounter this problem:
1) I test my app thoroughly on many devices. Use Analyze and Instruments. No crashes. All fine.
2) Submit it to the App Store. App creashes all the time.
I realize the "release build" is something a little bit different than the "debug build". But how can I test a release build on my device that is built exactly the way it will appear on the App Store, technically?Answer1:
I recommend you to use TestFlight (<a href="https://testflightapp.com/" rel="nofollow">https://testflightapp.com/</a>), I have been working with it recently and it is a great way to test your Apps before going public.
You would be using the final IPA file, so won't be any difference with the build you would submit to the AppStore... Also, you could invite other people and they could download and install your App over the air, and even more, you have remote logs about crashes...
Hope it helps you.Answer2:
You can of course also <strong>archive your build</strong> (set the scheme to <em>iOS Device</em>, then choose <em>Product -> Archive</em>) to an IPA, sign it with your <em>Ad-Hoc distribution profile</em>, and <strong>install it on your device</strong> by dragging the IPA file onto your device in the Xcode Organizer.
When your Archive scheme is set to build in RELEASE mode, this is as close as you can get to test your final app without going to the App Store.
Testflight is doing the same thing, as you have to upload the same IPA to their website, so if you do not need to involve more people you can just do it local this way.Answer3:
You can set your testing Scheme (under the Project menu) to build and run a release build. Or you can install an Ad Hoc build using iTunes if you want to test exactly the same install method as the reviewer.