Can we give multiple versions which we are going to release subsequently of the same application for the testers to test it in iTunes Connect.
As anyone effectively using this iTunes Connect Tesflight beta Testing?
Can you please direct me to any good tutorial on how to use it?
I found this tutorial,and it sounds pretty good:
Testflight Beta Testing
Video Tutorial to learn the beta testing
https://itunesconnect.apple.com/downloads/Documentation/TestFlight-v09-iTC-Export-sw.mov
Yes, you can upload different builds of same application to iTune connect for that you have to ensure that build numbers should be different otherwise you cant upload your build to iTune connect
https://developer.apple.com/library/ios/documentation/LanguagesUtilities/Conceptual/iTunesConnect_Guide/Chapters/BetaTestingTheApp.html#//apple_ref/doc/uid/TP40011225-CH35-SW2
I don't think it's possible to have multiple versions of your app available for TestFlight. As far as I know you can only have two versions available. Your current version and the following version. After you've created a new version of your current app the 'new version' button disappears.
You can provide multiple versions of your app each version will be available to the testers for a period of 30 days.
Related
I have an existing project. I also have a basic version of the app approved for beta testing.
How can I install this "TestFlight" beta version as a separate app to my device? So that I still have the version that I'm developing?
I read through some articles, they're saying you need to have different App ID's. But I'm not sure if that's what I need (could be, I don't know)
Example article: nilsou.com - How to have two versions of the same app on your device
There, I have to create a new APP ID for the beta version (though in my case I think I have to add 2 ID's, one for XCode versions and one for beta versions).
But does that mean I have to create a new app inside of iTunes Connect?
I thought iTunes Connect works with these APP IDs. What if I now have multiple APP ID's for my app?
Thanks in advance!
Maybe I have a stupid question, but after the update to Xcode 7, I sent a new version of my app to the App Store (via standard: Archives - Organizer - Upload to App Store). But now it is my build in iTunes Connect in tab Prerelease with status Processing (btw more than 12 hours), and I do not know why. Why is my build in Prereleasse tab? Previously, I uploaded new build the same way and I could have it for a few minutes to submit for review. Thx for help.
Update: After more than 48 hours, I can finally submit my new build for review! ;-)
The issue seems to be related specifically to Xcode 7. Some people have mentioned these work arounds to get it to go:
1) Use Application Loader and not Xcode to submit to iTunes.
2) Re-submit with new Xcode 7.1 beta.
3) Re-submit with old Xcode 6.4.
Your milage may vary.
Edit: Problem seems to be solved now, it appears to have been related to that exploited Xcode issue in China which caused significant iTunes Connect delays.
It's not the feature of Xcode, instead it's actually a feature of iTunes connect by itself.
All your uploaded archives go directly to "Prerelease" tab and lets you the privilege to distribute those to some specific users for beta testing, through TestFlight(optional), before you actually set it for production.
This process lets you debug your app performance and lets you actually maintain a build log, without actually releasing the app for public. When you are all set, you pick the best from Prerelease builds and release that to actual production environment, for public.
More documentation from Apple is available here
And by the way, I think your Processing issue should be automatically resolved if you give it some time (possibly 24 hours or so) or you might need to remove your app and upload that once more. You might know, Apple is too much busy to maintain it's App Store's security, right now ;)!!!
I can see from my iTunes connect control panel how many users are on each version of the app I have in beta. When does TestFlight update those apps? Do they have to open TestFlight and manually choose to update? Does it happen automatically when they launch the app they are testing?
I can't seem to find any answer on Apple's documentation.
They have to manually update it. A push notification and email is sent to let the user know that a new version is ready to be tested, but it's up to user to open test flight and install it.
As of November 11, 2020, TestFlight version 3.0 now supports automatic updates:
Source: https://www.macrumors.com/2020/11/11/testflight-app-automatic-update/
After a while, I found a solution that works every time.
You need to remove the version from testing by selecting Not Available for Testing. Then save, approve and reselect the version you want to test and save again.
This will make all your TestFlight users receive a notification with the update (event if they have a different version installed).
It might be possible to do a force upgrade, see https://stackoverflow.com/a/12319198/330067, however I didn't find any details so far.
I couldn't find anything about enterprise beta testing in the iTunes Connect Developer Guide so I hope this question doesn't seem too out of place here. Also, it says here that even the beta will be subject to a review. We are using private APIs so the app will not pass the review.
What I want to be able to do is continue beta testing our enterprise apps without any AppStore reviews. Can I do this on iTunes Connect or do I have to find an alternative now? If its the second, then could you please recommend any possible alternatives. Thanks in advance!
Let's see if Apple is coming up with some updates to the current version. It's not only the Enterprise testing support that is missing ...
But you can easily jump to another Beta Distribution Platform, some free, some paid, some freemium:
https://crashlytics.com/
http://www.hockeyapp.com/
http://ubertesters.com/
https://www.testfairy.com/
http://www.applause.com/mobile-sdk
https://appblade.com/
http://www.installrapp.com/
https://deploygate.com/
... and probably others I don't know.
Or you could host your own:
http://www.hanchorllc.com/betabuilder-for-ios/
http://hockeykit.net/
I personally switched to Crashlytics, it covers all that I need and it's free. Some things are better than in TestFlight, some aren't as good. But your choice might be different - some other platforms offer crowd testing for example or premium in-app test features.
You will never pass the AppStore review when using private APIs. Thus the only possible solution is to switch to alternatives. TF is not for enterprise app testing and we need to take it as it is.
I found nice article on beta testing enterprise apps without AppStore review, not sure if it is something you were looking for, but the main point is the same as yours. When testing enterprise app, you need to support different OSs (not only iOS 8) and you need to distribute your build without any reviews. Today TF is going to shutdown these both features.
Trying to upload build with TF SDK I see the following error message:
Sorry, we are no longer accepting any new builds that use TestFlight SDK. Please, remove SDK and re-upload.
Does anybody know any information about this? How long it will be like that? Will it be fixed? Am I doing something wrong? Interesting, that in another TF team everything is ok and upload with SDK goes with success.
TestFlight was acquired by Apple. Android has also been disabled for TestFlight.
See the news here.
Don't worry about it. Use another mobile beta testing like
Ubertesters
Hockeyapp
Mobtest
Centercode
Appmuse
AppHost
Diawi
Burly the parent company of TestFlight was acquired by Apple a couple of weeks back. TF accepts uploads with SDK for older teams, if it is a new team that option is no longer available.
You can still distribute builds to testers though. Just remove TestFlight SDK and remove takeOff code and upload it without SDK. Obviously you lose all the SKD features, but at least you can distribute.
Here is the official announcement from TestFlight.
http://help.testflightapp.com/customer/portal/articles/1452760
If you are using the SDK for crash log reporting, have a look at Crashlytics (owned by Twitter and completely free).