I'm trying to use Apple's new TestFlight beta testing program and I am getting hung up on adding a second build.
I began the whole process by creating a new app version for submission (1.4). It now sits in the Prepare For Submission state.
My first prerelease build, uploaded through xcode, was version 1.4. I was able to add testers and distribute without any problems. Cool.
Now I am trying to add a second beta - When I first tried, I was denied because of a 'redundant binary upload' -- I was using the same bundle version number. So I incremented it to 1.4.1 and added that build.
Now that the build is added, however, I am unable to add any testers to this second upload. I keep seeing this:
However, when I go to the builds page, I see the testers I've already added!
Why can i not distribute this second version???
You have to change the "Bundle Version" (aka the Build version) in your info.plist. Alternatively, you can go to your project Target, select the General tab, and update the "Build" there. Updating either location will update both locations.
Then the steps are the same as when you uploaded your first build for beta. I just went through this process and it went off without a hitch.
Related
I tried to publish the app to Apple Store Connect. Normally there is a "+" button but I don't see one right now because Apple have updated iTunes Connect and introduced a bug. How can I get around this bug and select a build to submit my app to the App Store.
I cannot choose the build to Submit for review.
I just uploaded a new version a few days ago, and everything seems to be working just fine on iTunes Connect. Could you please make sure you're following the steps below:
First create a build from Xcode with a specific version number (for instance 1.3.0), archive and upload to iTunes Connect. Wait a few minutes for the build to process.
Once the build has finished processing, make sure it's available on iTunes Connect by navigating to My Apps/Activity/iOS Builds. If everything is okay you should see your new build "Version 1.3.0" here.
Now before you can change the build, and this may be the step you're missing, you need to add a new version of your app for submission, via "+ Version or Platform". This number should match the build you uploaded earlier (1.3.0).
Then just select the newly created version of your app on the left menu, and you will have the option to select the new build you want to use for this version in the "Build" section.
I had the same problem. The Step 2 in #user13639548 answer confused me even more because I didn't find activity/ios builds.
What solved the problem however was changing the versin from 1.1 to 1.1.0. and then also waiting 3-5 more minutes until the + button appears again.
I made a new build of my app (version 2.2 build 11) and uploaded to App Store Connect.
Then I used "(+) Version or platform" to prepare version 2.2 for submission. When I press "Submit for Review", I get a warning:
Newer Build Available
Are you sure you want to submit this build for review? A newer build of your app is available. To submit the newer build, delete this earlier build and resubmit.
The currently released version of the app is 2.1. The "Activity" tab of App Store Connect only shows this build (11) for version 2.2. Build 10 was version 2.1.
What does this error actually mean, and how am I meant to resolve it? The obvious thing is to try deleting this build and resubmitting it, but I'd like to understand more about the error, especially if it turns out deleting and resubmitting doesn't help (haven't tried yet).
Solved it.
As an infrequent iOS developer, I thought that specifying the version number after hitting "(+) Version or platform" would be enough. But I missed actually choosing the build far down in the submission form.
Presumably it defaults to the previously submitted build, which in this case would be 2.1 build 10, causing the error.
So the error message could have been better, but it was ultimately something I missed.
Check Activity tab, if it says 'Processing` than you will not be able to add the build to the release, and you will get this error message.
Wait for about 10, minutes for it to complete, add your build to the release, and you are good to go.
I have successfully uploaded my iOS build on App Store today. Its been more then 5 hours now and the build is still not shown in Activities. I am using Xcode 10.1 to upload build and uploaded build using Xcode update build option. What needs to be done. I have tried to upload the same build again, but got "Redundant binary upload" error.
I had a similar issue. I upload a version with build number 2 and it was totally disappeared, I didn't find it anywhere and I can not re-upload it. I upload another build with number 3.
My app was approved and everything is okay. Today I received an email from Apple which said that I already have a build with a bigger version and I have to upload a new build bigger than 3.
I think somehow the service just hanged for a while(at least 2 days). But it hangs only the specific upload of build and it is not affecting the app.
You have several options:
Just wait
Create a new build with a bigger build number
Create a new version.
I did the second option and it was okay
Change the version of the app for example if it was 1.0 -> change it to 1.0.1 or 1.1
But you don't have to change the build if the app is not published to the App Store yet. Also make sure the build has been changed inside the .plist, that happens sometimes.
when you upload through Xcode to iTunesConnect it's can take a lot of time to process your build so just wait and it'll be finished eventually.
Recently I have noticed, that Apple's TestFlight app provides possibility to install older builds of application (application is during internal testing).
It is actually a nice feature, but is there any chance to remove some build that I don't want anybody to install anymore?
My case: I found some bug in app, that causes problems on a server-side - app simply overrides data. Problem in app is already solved in build X, but TestFlight still allow user to install build X-1.
I've tried:
found this option
stop & start testing
change app version (from 0.1 to 0.2) but builds of version 0.1 are still available - probably until expiration date (60 days from
upload)
Under TestFlight builds (ios),
If you have multiple builds, select the bad one.
Next expire the build, currently on the righthand side of the screen.
This does not solve the problem. The problem is that if you have "Manage Version and Build Number" checked in XCode Distribute App, it will create a new build number for you if you forgot to update it before you Archived. Consequently, builds can be uploaded to TestFlight and assigned a new number which you may not want - such as when XCode Distribute seems to have shown an error but actually has uploaded the build anyway.
In our case, we need to keep the build numbers in sync with our Android builds using Flutter. Yes, you can expire a build, but that build stays there and you can't delete it!!! Is there ANY way to actually DELETE the build, not merely expire it???
I am having a consistent problem with multiple different apps that the build on the device does not update when I make code changes. Here's my set up:
OSX Lion
Xcode 4.1
iOS 4.3.5
I build, and then run, the app launches on the device but it still runs the last installed version. In order to get the build to update, I have to do the following...
Remove the app from the device (press and hold on the icon, and click the x)
Clean and then build in Xcode
At this point if I try and run the app does not run. Xcode log says the app has started and stopped. If I restart Xcode and run, then the app runs successfully and is the updated version
If I make a single line of code change I have to go through all the steps above to get the app to update. The project is very large so a clean build takes 2-3 minutes.
Any ideas?
Update
I found the solution, this is related to the use of static libraries. The following article helped me solve this:
Changing the source of a static library needs clean and build in xcode 4
and for general background this was very helpful too:
http://blog.carbonfive.com/2011/04/04/using-open-source-static-libraries-in-xcode-4/
Double check your provisioning files and targets. Be extra sure to check the App ID in your targets, and Bundle ID in info.plist. Did you change any of that info before you saw this problem? I've noticed strange behavior like what you mentioned when updating those specific pieces of data.
Command+Shift+K -- Clean. I have found that you have to do a manual clean every time now to ensure that the build updates correctly.
In the event that xCode does not run at all, you just have to restart xCode.