My connection was dropped while I am uploading the archive to the apps store.. and it showed Uploaded successfully with big green tick..
And also it goes to the app store and wait forever in the processing state. So I just uploaded it with the new build number and it's processed within less than 10 minutes.
but troubles are not over :(
then I couldn't select my latest build for test it still showed that stuck one..
What can I do for this ?
====================================================================
This has happened to me a few times already i.e. when a binary doesn't finish processing due to connection drop or other issues (on apple side).
Just upload a new build and use that build for release or test flight. Don't worry about the build that never finishes. Just ignore it and move on.
If you are still seeing build 2 as the latest under testfligth section, then logout, clear your browser cache, log back in and see. Clearly your build 3 is the latest one. itunesconnect is super flaky.
Use apple support as a last resort. They will take days to solve something as simple as this.
In my experience when the build stays greyed out and (processing) for longer than a few minutes it will stay forever like that. Best to just re-upload and wait for the new build to process. It does take a bit of time to show up for testing though.
These are the steps which I did to got build to the testflight internal testers
to show Export Compliance add below line
to info.plist
<key>ITSAppUsesNonExemptEncryption</key><false/>
change version no to different one (not the build no)
create archive and upload it without upload bitcode enable tick
Related
I archived a new version of application on XCode and uploaded it on app store using XCode , however when I open all builds from app store connect , I am not able to find the build. Thus I am not able to choose the build on the version. to submit for review.
I'm having the same issue as well, it has been 20 hours since I upload my build when I'm writing this and it's still nowhere to be seen.
I also tried to upload a second build and it's also not showing.
So I believe it's an Apple issue and not isolated, looks like we can only wait for now.
Edit: It works now. I assume it works for everyone now.
I also had this issue this morning. I have just now uploaded a new build of my app and the new build now appears, the missing one still doesn't appear. You will need to change the version number and re-archive your app, as otherwise it will be rejected as a redundant upload.
Update after 10 minutes the new build also disappears. Awesome..
After archieved file uploaded successfully it will go into processing stage. Where they are checking the internal settings using the automated tools.
Things will be checked like if any permission issues coming etc.
Lets say of example if you are using camera into your application but you have not given permission into.plist file than it will get failed into processing & removed build from the App Store.
Also if you have set up the permission properly but not given instructions that how & why this gets used than also build will get failed into processing stage. So there can be various reasons.
Ofcourse they will send you an email to your Admin email Id about the build failed while processing with the reason so by that you can resolve the issue.
Hope this will helps to everyone.
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 have successfully built and uploaded a new version of an app with Xcode 7.3.1 in OS X 10.11.5, but the build is not showing in iTunes Connect.
After the build process (launched through the "product->archive" menu) the Organizer opens.
There, I choose the build and click on "Upload to App Store..."
So far, everything works as expected.
After the upload, when I refresh the iTunes Connect web page (under the "Activity" tab), I briefly see the new build showing in the list.
If I refresh the page again, some seconds later, the build has disappeared. I can no longer find it anywhere in the iTunes Connect site.
When I try to repeat the process, XCode gives the following error message:
ERROR ITMS-4238: "Redundant Binary Upload. There already exists a
binary upload with build version '2.4' for train '1.5'" at
SoftwareAssets/PreReleaseSoftwareAsset
so I have to increase the version number to complete another upload.
I went through this process 3 times, the last one using Application Loader instead of XCode, but the same thing happened all the times.
Does anyone know why this is happening?
What could I do to troubleshoot this problem?
What other informations may be useful to further investigate?
UPDATE
More than 48 hours have passed since the first upload, still no signs of any builds in iTunes Connect.
The only thing I can tell you is that it's probably a matter of time. I faced the same issue weeks ago, and between 24 and 48 hours after submitting, my build was finally showing in iTunes Connect.
It's a shame for Apple to make developers wait without informations... But this kind of issue had been reported a lot.
It turned out to be a wrong icon included in the asset catalog.
After 5 days of troubleshooting and ping pong with the Apple support, I was finally pointed in the right direction. All I had to do was replacing an image that was the wrong size.
Done that, all worked as expected.
On new iTunes Connect after upgrading Xcode to 7.0 version I can't select my build after uploading it from Xcode.
Hanged on weird (Processing) Status as you may see in the picture below.
And it keeps unselectable.
Thanks.
It's not a problem related with Xcode 7 or the new iTunes Connect I think, it happened before but now I see it happens more often (based on the questions in these days on StackOverflow); some months ago I had my build stuck in processing for over 6 days.
I know this it's terrible but normally this processing state if happens it takes 20 minutes about and after that you can select you build.
If you have problems or the process takes too much time you can contact Apple.
Had the same problem many times, it was a time sensitive app I needed to get online, I re-archived my app in Xcode with a higher version, and uploaded it to the app store, when doing this, my build was no longer processing and I could select it (the new one was processing but the original version that I wanted was then available) it's very annoying to have to re-archive and upload another identical version, but it was the only way I found to get a build out of processing quickly.
I hope this helps!
Beau