I uploaded an app on Testflight using Xcode (Build 1.1.0) and it was available to the testers. But now this version has been expired and new versions (1.1.1 - 1.1.3) are not available to them:
I have tried opening the newer build links and it says:
I clearly have Internal testers added to my account. How can I fix this problem and make the latest builds accessible to the developers?
Follow the steps indicated in image and you can add testers and then select your app version and build for testing and added user will get notification for that.
Related
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.
I'm publishing my first Xamarin.iOS app to the store. I've set up my distribution profiles, set up the app on iTunes connect, and all seems well. I published my app for archiving and then successfully uploaded via the Application Loader.
What's broke is that iTunes Connect doesn't see my app - it says I still need to upload via Xcode or Application Loader... but when I try to upload my IPA (again) via the Application loader ("sign and distribute" via Xamarin), I get the error "ERROR ITMS-4238: "Redundant Binary Upload. There already exists a binary upload with build version '1.0' for train '1.0'" at SoftwareAssets/PreReleaseSoftwareAsset."
I don't see an option in ITunesConnect to delete this build and start over with another version, and it won't let me Submit for Review because it doesn't see the build as being uploaded.
I've opened a ticket with Apple over a week ago and haven't heard back. I know I could go with a different AppId but for all I know I'll hit the same wall. Anybody been down this road?
UPDATE #1
I've created version 1.1 of my app and uploaded it successfully to ITC. I see it in the Builds section (still don't see 1.0) but I can't add a new version of the app to "link" this build to because v1.0 is still "Preparing to Submit"
Apps - unable to create v1.1 while v1.0 is "Preparing to Submit."
Builds - v1.0 is not visible, but if I try to reupload ITC says it's there
UPDATE #2
I was able to link v1.0 of my app store submission to v1.1 build and submit the app for review. I don't know if this will go through or not, but it was at least submitted. I am now also able to "reject" this version, but if I do this I'm unable to add another version still (if I wanted to get a clean v1.1).
Each build you upload must have a unique build number. So if you upload 1.0 then the next must be 1.1 etc. What I do is keep the internal test builds with an extra .1 at the end so my internal would be 1.1.1, 1.1.2 etc and then I'll push 1.2 to the store when ready. You can also change the version number on your App's settings on iTunes Connect. They wont reject it as it's just the build number.
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.
I have a build installed from TestFlight on ios device. I am not able to open this app. I have not accepted the invite for next version. Does INSTALLED build get invalidate after new version is released from TestFlight? What is the behaviour for Internal and external testers in this case?
We have had a number of our app's TestFlight users report that after updating iOS they can't open the app. We had to send them a new build to get things working.
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