In iTunes Connect, under the Activity - All builds, I can see all the versions uploaded to the iTunes Connect. But I am not able to distribute an older version for internal testing.
Under the TestFlight - Select Version => I can see only the last version, but not any from the previous ones.
From iTunes Connect:
Internal testers have access to the latest build for the selected version. They’ll also have access to any new builds that you upload for this version.
I would like to ask whether it is possible to distribute an older version via TestFlight.
Thank you for any help.
Best
Matti
Are you the builds older than 60 days? if so they cannot. They expire at this time. If they are less than 60 days you should be able to select that build.
Related
I'm not very familiar with TestFlight. I would like to add a build with a new version for my app. Do I need to add the new version to the App Store settings first?
For every build you upload to iTunes Connect you can decide whether you want to share it with testers on TestFlight and/or submit it for app store review.
When you share builds with TestFlight Apple will review these builds too and you can receive warnings to them too. The initial TestFlight build will be tested more extensively.
Do I need to add the new version to the App Store settings first?
I don't know about which app store settings you are talking about, but all you have to do before uploading to iTunes connect is set the code signing and provisioning profiles first in XCode and Apple's development portal and make sure you increment the build number on every new upload because the upload will fail if you try to upload a build with a build number already present on iTunes Connect.
Once uploaded iTunes Connect will start processing it and then you can share it for testing with TestFlight or submit for app store release review.
You can read more info about TestFlight in Apple's dev site
1 - Test Flight have nothing to do with Live apps
2 - Versions can contain unlimited number of builds before submitting one to the Live app store
3 - Every time you upload new build it goes under the version number in test flight.
So lets say I am on version 1.0, everyday I'am uploading new build under the same version number
day one : 1.0 (1)
day two: 1.0 (2)
And so on, after i upload the final build i can submit that to the live app store, next i will start working on version 1.1 I add that and submit builds to test flight as before, then i submit my 1.1 to the store, and so on .
On app store users will not see anything but the version submitted and current version live is not affected by any test flight version, i can be on version 9 on test flight but 3 on app store, and even schedule an update every month till i reach 9.
I'm going to submit my app to AppStore soon. But I'm wondering if my beta testers will still be able to use new TestFlight builds and the build from AppStore simultaneously after approval (my app supports push notifications). Is it possible without two different bundle ids?
Is the only solution to uninstall AppStore version and install new from TestFlight?
It is not possible for them to use both. When the new TestFlight build is installed it will upgrade the AppStore version that is already installed. The user will be able to re-download the AppStore version and over-write the TestFlight version. One thing to be careful of is that the old version can still read any files written by the new version. E.g. if you changed the file format in the new version then re-installing the old version may cause it to have issues if it can't read the new file format.
They will still be able to use the TestFlight builds. I believe they will have to uninstall the AppStore version.
Our company is currently running a beta test using TestFlight, and we're looking to push a new build that has several major changes. We'd like to test to make sure nothing's catastrophically wrong with the new build before pushing it, but unfortunately many people here work remotely and we can't manually install the new build on their devices.
What I'd like to do is upload a new build to iTunes Connect, and not submit it for review until we've had a chance to test it. According to Apple:
As you upload new builds for a prerelease version, internal testers will always get the most recent build you uploaded. External testers get access to the update only after you have submitted it to Beta App Review and it has been approved.
This is good. This is exactly what I want. However, on the next line, they go on to say:
Uploading a new build will automatically disable new installations of older builds.
What I'm understanding that to mean is that if you upload a new internal build, nobody will be able to install the old external build. Is that right? And if so, is there any way to have a second, internal test version?
I see your misunderstanding here. How it works is that when you upload a new build, all your Internal Testers will be notified and be able to download the new version. Only fro internal testers the previous version will be disabled, while external testers will be able to download the last reviewed version of your app for up to 30 days. Only when you'll also submit your new build for external testing review you will update your external tester's version. Until then they'll be able to download the current version. Hope that helps,
Julian
now i am using test flight for testing my application.Testflight said from next month onwards standard test flight is not available.SO i have some doubt on this please clarify
-Standard test flight is available for already existing apps or not?If available can i release new build?
-How can i test the ios 7 apps with test flight beta testing.
-Apple saying,each prerelease version expires after 30 days.So after 30 days can i test downloaded app?
-Suppose i released build A and installed in some devices and after 10 days again i released build B and installed on some other devices.Both are working or only latest Build B is working?
-Each internal tester can test the app in 10 devices,So how we can register that devices.
-Each version we have to wait for beta app review for external testers?
If any information is useful for me please post except these questions.
-Standard test flight is available for already existing apps or not?If available can i release new build?
The original TestFlight is being shut down. Apple's TestFlight is the new TestFlight and you can use it with existing apps.
-How can i test the ios 7 apps with test flight beta testing.
You can't. TestFlight is iOS 8 only.
-Apple saying,each prerelease version expires after 30 days.So after 30 days can i test downloaded app?
This means that the build expires in 30 days. You have to keep submitting new builds for your testers.
I find this good way to keep your testers really up to date and up to the task. In contrast, if build didn't expire, the beta testers could stick to the old versions and eventually become a burden (irrelevant bug reports, etc.).
-Suppose i released build A and installed in some devices and after 10 days again i released build B and installed on some other devices.Both are working or only latest Build B is working?
I think the old build A will continue working for the aforementioned 30 days when you submit the new build. You simply can't revert back to it. I'm not absolutely sure though, but there is a transition time for beta testers to update to the new version.
-Each internal tester can test the app in 10 devices,So how we can register that devices.
I haven't had any internal testers but my guess is that the usual way: add the devices from the developer portal.
-Each version we have to wait for beta app review for external testers?
Yes. However, if the new builds have no major modifications they might not need to wait for the review process. This is being asked when you submit consecutive builds.
I think there is a chance of review even with small updates, but I haven't seen any. I've had new builds ready to distribute within the same hour every time I submit a minor update.
Recently, the All-New TestFlight Beta Testing service was launched inside of iTunes Connect.
Here's What's New:
Invite up to 1,000 external testers using just their email address
Easy to use TestFlight iOS app available on the App Store
No need to keep track of UDIDs or provisioning profiles
Beta testing directly inside of iTunes Connect without the need of the TestFlight SDK
Learn more »
With the new version of the TestFlight service available inside of iTunes Connect, we are also informing you that TestFlightapp.com will no longer be available as of 2/26/2015.
To prepare for the TestFlightapp.com closure, we recommend that you export all of your current testers so you can import them directly into the new TestFlight Beta Testing service.
How to export testers from TestFlightapp.com
Sign in to the TestFlight Dashboard at testflightapp.com
Navigate to the "People" tab
Check mark the teammates you would like to export
Open the "Actions" menu on the right side of the teammates list
Select "Export Contact Info" to download the exported CSV file
How to import testers into the new TestFlight Beta Testing
Sign in to iTunes Connect at itunesconnect.apple.com
Click "My Apps"
Select the app you want to enable for beta testing
Enter the "Prerelease" tab and select "External Testers"
Click the plus sign to add new external testers
Use the "Import File" from the "Add New External Testers" page to upload the exported CSV file
Hope this information helps you.
-Standard test flight is available for already existing apps or not?If available can i release new build?
Standard Test flight app is completely shut down. You cannot use it anymore.
-How can i test the ios 7 apps with test flight beta testing.
Testflight beta testing is not available for iOS 7 apps.
-Apple saying,each prerelease version expires after 30 days.So after 30 days can i test downloaded app?
Yes, you can continue testing already downloaded app. 30 days is the active period for downloading app.
-Suppose i released build A and installed in some devices and after 10 days again i released build B and installed on some other devices.Both are working or only latest Build B is working?
Both will continue to work but after uploading release B, build A will be deactivated for downloading. Only latest uploaded builds will be active.
-Each internal tester can test the app in 10 devices,So how we can register that devices.
When you accept the invitation from any device, the device gets registered.
-Each version we have to wait for beta app review for external testers?
Yes, you need to wait for approval then only you can distribute app to external testers.
There are lots of extremely similar posts but I'm not sure if there are any exactly like this.
I changed the build number but kept the version the same. I uploaded it and now it shows two builds in iTunes Connect's app prerelease builds as expected. But on my internal testers' devices, it doesn't show any updates.
It's been a few hours now and still no change.
Had the same issue. If you turn off beta testing in iTunes Connect and turn it back on again, the builds in the TestFlight app will update, and users will get the notification. This way you don't need to change the version number.
Change build number and version number both to update build on iTunes Connect's .