For internal testing we want to install an old version on a device of someone who's UDID is not in the list. Via TestFlight I can add the email of this person in order for him to download the newest version (via internal testing), but I was wondering if it would be possible to enable him to download and install a specific old version?
I've seen this page: how to install previous version on TestFlight but it is rather old and the suggestions are incorrect.
I found a workaround to test older builds with TestFlight. You can just use the link provided in the email you received when you uploaded the older build for testing. You will see something like this.
To test this app, open TestFlight on your iOS device using iOS 8.0 or later and install the update.
Tap on "TestFlight" in the above line. This will open TestFlight with a link to the older build. And you can install it if it hasn't yet expired.
Hope this helps!
Update
As of April 11, 2017, TestFlight now supports multiple builds.
https://developer.apple.com/testflight/release-notes/
You can navigate to the Previous Builds section of the app in TestFlight and get access to builds which are up to 90 days old.
Latest working way to find previous builds:
tap on the app icon ( current one )
scroll to the bottom , you will see 'Previous builds'
Tap on it and you will see all previous builds.
Thanks
You can check in Testflight application, there is a section old builds, under that section you can see old builds.
In the TestFlight we can check for the old build in that we can select the particular build.
[Please find the screen shot for reference]
Related
I uploaded a new build to AppStoreConnect. I was able to test it through TestFlight.
I sent the build to review, it was approved. Then when I tried to open the test app on my device and got the above error:
The status on TestFlight seems to be "Ready for Submit, expires in 86 days".
I tried to remove the app, and reinstall it from TestFlight. Then I got this:
Restarting the phone, or trying to install it from a different device leads to the same problem.
Why does that happen? Is it an Apple-side bug?
What is the workaround for this issue?
It seems to be a bug in TestFlight and/or iOS.
It happens when you upload a new version with automatic updates. Installing the app manually seems to be just fine.
Consider downgrading to a previous build and then manually updating it or uploading and installing a new build. Both options should solve this issue.
It started to happen in late October 2022, and it is still happening to our builds as of November 2022.
You need to upload a new version onto test flight or add a new app directly with your mac so that it does not use testflight at all.
I built my latest release of my iPhone app. I used XCode to build it, archive it and publish it.
Usually I see the latest build in the Apple store connect. This time it doesn't show up and I don't know why:
You can check the status of you uploaded builds under Activity. Maybe there's something wrong with your upload.
Usually you need to wait a few minutes for apple to process your uploaded version.
Also try to hover over Build in your screenshot. A blue + button should appear there.
Your assumption, that you need to increment the deployment target is wrong.
You only need the Xcode 10.1 (or higher) build tools. The deployment target is the minimum iOS version which you support. So building for iOS target 9.0 with Xcode 10.1 should also work.
I just fixed the problem,
Till now, in XCode, under the deployment info, I had "Deployment Target = 9.1". I tried setting it to "10.1" and now my new builds show up on the online Apple developer page.
To solve the issue I had to go through the Apple help page, where I found that from now on, Apple only accepts apps build with XCode 10.1 or later
Go to Activity and check the binary version which you have uploaded. Check the status. The newer binary still is in the waiting process or have some issues. You should get a confirmation mail regarding successful uploads.
I keep on getting old build in Testflight even if I upload a new one. The version and build number is correct but the project build is always the old one.
Solved the problem, it’s the versioning of the build. Appstore doesnt recognize that 0.0.2 is newer that 0.0.1. It should be of two digits. When I tried 0.0.30 it solved the issue that it must email the testers that new build is available, but upon installing still old build is provided. I opted to go for 0.1.00 as our base version, it worked. Dont know why appstore behave like this.
Some background of the issue:
I have a Xcode project named A. It has a bundle ID com.abc.tung. It was on AppStore already and had few app version updates with no issues.
Later we decided to re-write the app and create a new project in Xcode named B. We also gave it the same bundle ID com.abc.tung. We uploaded a new build to AppStore Connect, everything was fine, it went to correct app in the AppStore Connect. Then we released it to AppStore.
The problem:
Some of the users reported an issue that even after the update to the newest version (the version that came from project B), it would still open them an old app with old functionality.
Please help me to understand how is it possible? Or even if you had similar issues, please also comment since it might also be some issues with AppStore?
Since bundle ID hasn't changed, it might be a build version question.
Need to find out what app build version was submitted to AppStore as B, and what build version was installed on the device.
The version on iOS is the release version (like 1.2.3) + a build number (can be just a single number like 4), so the full build version looks like 1.2.3(4).
It is a good idea to display the full version inside the app UI to make it easier for the end users to report it to you.
I have recently uploaded a build in AppStore(TestFlight) and got the following mail from AppStore,
Dear developer,
We have discovered one or more issues with your recent delivery for
"MY APP". Your delivery was successful, but you may wish to correct
the following issues in your next delivery:
Deprecated Xcode Build - Due to resolved app archives issues, we will
be deprecating Xcode 8.3 on May 10, 2017, at which time app archives
built with 8.3 will no longer be accepted by the App Store. Download
Xcode 8.3.2 or newer, rebuild your app and resubmit.
After you’ve corrected the issues, you can use Xcode or Application
Loader to upload a new binary to iTunes Connect.
Regards,
The App Store team
Will there be any problem on releasing the current build for review ?
Or
Do I want to download the latest Xcode version as mentioned in the mail and upload an another build ?
Will there be any problem on releasing the current build for review?
If you submit your app for review and will be reviewed successfully before the May 10, 2017, than you do not need to do anything with you current build.
Do I want to download the latest Xcode version as mentioned in the mail and upload an another build ?
You should be updating to the latest Xcode anyway, at least for the sake of having all the latest tools and API's available. If you would like to submit a new build after the May 10, 2017, you have to update Xcode, rebuild the app and submit a different binary for Apple to review.
Overall, i would recommend to update now, and submit a different build, because you will have to do it anyway in the near future, and your app will not be rejected because of the Deprecated Xcode Build issue for sure.
EDIT:
Xcode 8.3.2 is available in the App Store.