I´m trying to upload an app with Codemagic and it goes wrong in the post processing stage App Store distribution, after almost 30 tries to find a build matching uploaded version yet, says this:
The application binary was successfully uploaded to App Store Connect for processing but the corresponding build is not available in App Store Connect. This usually happens when the uploaded application has one or more issues. Please check your email for direct feedback from Apple.
And they send me a mail saying:
"Swift Support it´s invalid: The SwiftSupport floder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it."
I tried changing the "Embedded Content Contains Swift Code", the "BUILD_LIBRARY_FOR_DISTRIBUTION" and the "DEFINES_MODULE" fields but nothing change. Don´t know if its a problem of Codemagic or Apple.
Try changing the version code and uploading again, it happened to me too. However, uploading a new build seemed to work without issues. App Store Connect team revealed that there was a brief issue where some apps received this error.
You can read other developer's experiences on the Apple Developer forums at this link
Related
I created an archive for app release.
But no matter how much time passes, nothing appears in the build window.
What should I do
+)I have a Team and make a identifier, certificate for team.
I even uploaded the archive file successfully.
But in App store connect, Nothing is shown.
This may happen if your uploaded archive couldn't pass through the initial processing of the build that occurs as soon as it is uploaded.
I once got stuck with this because my app had some legacy code that was using UIWebview which is now deprecated.
You'll always receive some comment from apple if this happens (through email).
i'm trying to upgrade an iOs App on the App Store by releasing a new version. I've the iTunes Connect Account and I'm working on Xcode.
I've updated the Version and Build values from 1.0.15 to 1.0.16 in the Identity Section of my app *-Info.plist
Then I uploaded the build to the iTunes Connect from Xcode by doing:
Product -> Archive -> Validate -> and then Upload to the App Store...->
I selected the automatic signing authentication and chosen the App Team for profiling that I want the build to be uploaded to.
Xcode has uploaded the build to the iTunes Connect and no error have been thrown.
Now, when I go to my iOs build on the App Store, I expect to find it, but there isn't.
When I upload it again I now have this error:
It seems that the Apple Server already got the release.
So? Where is my build gone? How can I found it?
I read in some SO threads that there was a Prerelease View in the iTunes Connect but I'm unable to find it any more. Maybe it has been replaced?
EDIT 1
This is my Build iOs on iTunes Connect view.
The open tab is the previous build, my new one 1.0.16 it is not present in the list and I can't find it anywhere..
I knew that I could upload a newer version by incrementing the version and build.
If it will not appear soon I will assume an error occurred and try to submit a new one.
EDIT 2
One week has passed and the build hasn't appeared. So I have uploaded a new upgraded version to 1.0.17, but it's still not appearing in my activity tab.
I would like to point out that before loading the previus 1.0.16 version, I had already created a new app version in the App Store Tab.
Can this possibly causes the issue?
What else can it be?
I'm gonna wait a little more and if not appearing i'll open a support ticket.
Solution: check your email !
After days of waiting I discovered that my iTunes Connect associated email address had received feedback from the iTunes Store Team. The emails said there was issues on the app (Missing Info.plist key) that prevented the delivery to be processed.
It is important to check your email address from apple communications because some of that information cannot be found elsewhere!
If the build is uploaded to appstore, then it will take some time normally. In the mean time You can see your newly uploaded build in the activity section under the version of the app with a processing label in brackets(see ).
Once uploaded build with a version number and build number cannot be uploaded to appstore again.If you want to upload new build to appstore, then either change the version or build number and try again.
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.
Documentation on the Monaca site for submitting an iOS app to App Store is not consistent with what I'm seeing on iTunes Connect. I have an individual account, so I don't have the option to submit as an Agent per the documentation. I'm thinking that explains why all subsequent steps in the Monaca documentation is different from what I'm seeing on iTunes Connect. I don't see an Upload Binary option for the binary build I downloaded from Monaca. The only option I see is to submit using Xcode or Application Loader. Any help pointing me to the proper way to submit is appreciated. Thanks.
The only way is to indeed use Application Loader or Xcode. I use Application Loader, personally. This means you must be using a Mac.
My problem is that after migrating project to XCode6 I just can't submit my app - it's permanently becomes "invalid" - get status "invalid binary" after 10-30 minutes.
Before migration there was no any troubles
There is no code modifications since old XCode version (5.1)
Most frustrating is as other users I received email from ITC
support, but it does not contains any details at all!
iTunes Connect
Dear XXX,
The status for the following app has changed to Invalid Binary.
App Name: XXX
App Version Number: 2.0
App SKU: XXX
App Apple ID:XXX
To make changes to this app, sign in to iTunes Connect and open the Manage Your Applications module.
If you have any questions regarding your app, click Contact Us in iTunes Connect.
Regards,
The iTunes Store team
I wrote email to ITC support, but there is still no answer. Any suggestions? It's hard to me find any reason cos app successfully passes validation during upload.
Large amount of tests lead me to next conclusion: one of third-party libraries (AppsFlyer) uses Advertising Identifier. I removed it from my app and for now all is ok.
I think this problem is because of new builds/prereleases system - things which previously lead to warnings during validation/uploading now are not appear.
So annoying...
I'm using several libraries which uses the AdvertiserId on several apps and the builds were submitted successfully.
When submitting the app, Apple ask 3 question about your app. The third is about using the Advertiser ID. Did you checked any of the options there? If not, You should....