Menu
I am using TestFlight - must I remove all the source code from my solution or is it okay just to comment out any calls to TestFlight before submitting to App Store?
416
After beta testing your final build, submit it to App Review, then offer it on the App Store. If you used TestFlight to distribute a beta version, and entered the additional information required by App Store for a release, just submit the last build that appears in App Store Connect to App Review.
TestFlight forces you to use your iTunes Apple ID, which means whenever I want to either go into TestFlight or go to buy music, I have to switch credentials.
TestFlight will tell you how many days until your current version expires. Once expired, you won't be able to use the Register app until you update to newer early access version or revert to the regular version of the Register app. To update to a newer early access version, open TestFlight and select Update.
The testflight library adds quite a bit of weight to your app, and it would seem sensible to remove it from your app store builds if you are not using it. Commenting out your calls is also rather cumbersome.
You can use a different build configuration which uses preprocessor definitions to prevent your testflight calls unless you have built for beta, this configuration can also exclude the test flight library from non-beta builds.
This also means that your simulator runs don't call testflight either, which is usually a good thing.
There is a good explanation of the process here which also refers this other question here on Stack Overflow.
175
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
