I have already gone through various similar questions asked here on Stack Overflow and also on other blogs. Unfortunately, none of those solutions are resolving my issue.
After doing a lot of search & when I was not able to solve my issue, I decided to ask you all.
I will explain scenario briefly. I have already uploaded iOS application for beta testing on iTunes Connect. My app's current status in iTunes Connect is "Expired" as 30 days testing period is over. I did few source code modifications and I want to make this updated application available for testers. Therefore, I tried to upload new build version for the app.
What I did is -
App version (Bundle versions string.short) - Not modified (1.0)
Bundle version - Modified from "1.1" to "1.1.1"
Build the application
Submitted application - Window -> Organizer -> Submit
Even though I did it properly, I am getting error as in below -
Can anyone of you please help me to understand where I might be doing mistake? Any help is appreciated.
Edit 1:
I tried to use build version 1.2/ 1.2.1 as well. Also I tried to upload a complete new app record in iTunes Connect with app version 2.0 and build version 2.1.0/ 210, but everytime got same error.
Edit 2:
My app's current status in iTunes Connect is "Expired". Will it matter while uploading new build version for same app? If yes, what could be the best solution for such issue?
Finally my issue got resolved. Along with modifying the Build version and keeping the Bundle version as it is, we need to check for few build settings whether they are set properly.
I was missing them and that is why I was not able to upload updated version of my application to iTunes Connect.
Please, refer below screen shot for these Build Setting.
You can find complete blog here - iOS 8 Beta testing with TestFlight
This helped me and I hope this will help few others.
Related
I'm currently making a react native application and need the user_link permission from Facebook. To do so, I have to submit an ios simulator build for app review.
I followed the instructions here https://developers.facebook.com/docs/ios/getting-started/advanced/ but my request got rejected for these two reasons:
Developer Policy 6.1 - Login
Developer Policy 1.9 - Build a Quality Product
Here's what I have done so far:
Ran my .app using ios-sim launch /path/to/.app since I did not do this previously and just directly submitted a ZIP of my DERIVEDDATA folder but
I encounter a "No bundle URL present." error, which I think is because I did not execute npx react-native start before hand (which I would have normally except I didn't becuase I launched the .app directly to the simulator)
I have reached out to Facebook App Review Support and talked to a live agent.
They were very helpful and pointed out that I should also have provided the path where to find my .app in the sea of folders inside the ZIP however, they could not provide a solution to fix the error I have since it's most probably react-native related.
Thank you very much! Any help is greatly appreciated!
I've had an iOS project in fairly stable condition up until Xcode 8's public release. After a bit of confusion with the Migrator, I finally convinced the compiler that I did not want to go Swift 3 yet, and that my code was indeed valid Swift 2.3. Not sure if this at all relates to what the Organizer does in validating my long-awaited archive with some long-overdue fixes for iOS 10, but we'll see...
Anyway, I got Xcode to archive my latest build (which runs fine on my iPhone 5s by the way). I tell Organizer to "Validate..." in preparation for an upload to iTunes Connect. After a good deal of doing its thing, it finally spits this at me:
Been at this for three days now. Application Loader gives me something similar, but not much more helpful:
Following the suggestions in this answer, I find that every single one of my compiled assets read as sRGB, not 16-bit, or P3. Aside: When does an API analysis file get "too large"? I mean, sure I use Apple's APIs a lot, but I can't be alone in that. That's what they're for, right?
I've tried (almost) everything I can think of. I've redone my code signing a dozen different ways, read and recombobulated the build settings wherever I thought could be relevant, and tried every combination of bitcode and symbol inclusion available to me. Just about everything I could come up with short of migrating to Swift 3! Could that really be my solution? It's a rather big jump, and with the time I have, I'd prefer to get this working build out to my users before I'm slammed too hard to shore up the updated codebase.
I can't seem to find anything on "ITunesSoftwareServiceAuthenticationErrorDomain", or this mysterious "error 434". The only reference I've found so far leads to a dead StackOverflow question. Really wish the author hadn't removed it... Wonder if he found his answer?
So my question is as follows: What am I doing wrong to get these errors, and how can I fix them? I'd rather not have to upload without symbols or bitcode, so if that's the workaround, I'd like to know why, so I'm not limiting myself for something dumb.
Cheers!
I had the same problem with Xcode 8.2 while submitting my application:
ITunesSoftwareServiceAuthenticationErrorDomain error 434.
Solution: I switched to different network and it worked for me.
Bump the build number and validate again.
Had the exact same problem. I tried upgrading to Sierra which seemed to update bits of Xcode etc. The new error message was formatted differently, so I could not see the "434"
(With 1 success in 15 attempts (I had to tweak a version number in a string in the app, so didn't choose to upload after that brief moment of joy), i just uploaded the archive anyway, and after 2 hours of processing, it was accepted. I will update when my new app version is live to verify this error can be safely ignored, at least in some cases (e.g. I checked all my graphics' color profiles, etc.).
Do the below steps :-
1. Analyze the project. (From Product Menu)
2. Click on Archive. (From Product Menu)
3. Select the development team for provisioning.
4. From summary window unselect "Include bitcode" and click on Validate button.
Now, It will working fine.
I solved it by uploading my app through Application Loader.
Archive app Export ipa iOS Deployment
Xcode-> open developer tool -> Application loader
I had the same problem while I was trying to submit the app to client's iTunesConnect account. I've signed in with new apple id, downloaded the certificates and provisionin profiles but still got this error:
(ITunesSoftwareServiceAuthenticationErrorDomain error 434.)
How to fix this error?
Try to remove Provisioning Profiles files at ~/Library/MobileDevice/Provisioning Profiles/
Make new Build and Archive the app. Xcode will create new Provisioning Profiles and submit the app to iTunesConnect.
Just to share this.
Quit xcode and re-login as suggested by members does not work for me. I solved it by using "Application Loader"
Steps: 1) change the version and build in your App 2) archive again for new file submission and export file to desktop 3) goto top menu: Open Developer Tool > Application Loader (if you don't have this , search, download and install this plug init) 4) upload the new version archived file. Done
You will find them in iTune Connect. From here process to My Apps > choose the rejected app > change the version and click on the new uploaded archive file, file will be processing..
5) time to resubmit :) cheers
Clicked Valid until it succeeded, 3rd time.
Since there seem to be many solutions to this problem, it may just be an issue not related to anything developers have control over and the "solutions" seem to be "solutions" because after some action was taken, it succeeded. The action I took was the non-action... and it was successful.
Hope this helps, as this is a stressful problem to have when you cannot upload your app and muddling around in Xcode to fix it you might break something else.
I fixed it by upload using Application Loader.
Besides, after upload the app i receive the warning about Privacy - Photo Library Usage Description and Privacy - Camera Usage Description, so that, please make sure you have them in your info
Hope it help!
I had the same problem. In my case it was caused by following. I had a lot of png-files in assets.xcassets and some of them had AdobeRGB Color profile. I changed the profiles to sRGB and xcode validated the archive with no error.
Frankly speaking, when I changed the profiles some other strange errors occured, but they dissapeared by themselves when I tried to re-validate the acrchive several hours later (I did nothing just waited).
If this occurred randomly, try to delete that archive and make sure you have "Generic iOS Device" selected as target when you run Product > Archive again. This solved it for me.
I Got the same issues when i try first time.Next time it Validated successfully. Please check network once before trying second time.
1.Cmd+Shift+K
2.Close Xcode
3.Open Xcode
4.Cmd+B
5.Product->Archive
Just Clear all file in Path ~/Library/MobileDevice/Provisioning Profiles
Go to Xcode Select Provisioning profile again and then it auto-generate again.
So It will be working fine.
In my case it was the following:
my account had been logged out and I had to enter the password again
Xcode v8.0 had to be updated to 9.x to be able to publish to the App Store (as of July 2018)
I fixed this problem by updating Xcode from 8.2 to 9.
Apparently there was a compatibility issue with an SDK used internally. Xcode was not helping with it's error message. I discovered it by using the Application Loader to upload the archive. Application Loader's error message made some sense.
I was having problem with uploading a build of my app but I was successful uploading a build (0.0.7) of version (1.0.0) while the build (0.0.6) was still processing
But when I am trying to add internal testers to test this build, the uploaded version is not showing up instead it shows the version which is still in processing.
Does it have something to do with iTunes or I am doing something wrong?
A guy from Apple contacted me after 12 hours with this e-mail
"Thank you for providing that information. In reviewing the information and screenshots you provided, I can see that you have a build that is stuck in processing and you were able to upload subsequent builds successfully, however you are unable to test the new builds.
We’ve had some reports of this issue and it should now be resolved. In order to continue testing, you will need to submit a new build with a new version. Once you submit a new build with a new version, you will have the new builds available to select from when choosing a build to test."
So, I think uploading a new build with a new version will hopefully work
I was able to resolve the issue by logging into iTunes Connect and removing myself as an internal tester (which removed the app from my TestFlight App) and then accepting the invitation again.
Try this :
1) Launch Application Loader.
2) In the top menu bar, click Application Loader > Preferences.
3) Choose Advanced.
4) Under Transfer Protocol, deselect Aspera.
5) Close the Preferences window and proceed with the delivery.
I am also facing the same issue and i change the version of my app in Xcode and then it will be shown in the internal testing. Please just change the version of your app then it will show. Just change the version to 1.0.1 or 1.1 whatever you want. Hope this will help you.
Thanks
Regards
Mandeep Singh
When I try to upload my app to iTC, after validate my app, I begin to submit it .
But there is an Error that said "iTunes Store operation failed
Error Description not available"
When I upload with Application Loader 3.0, same error happened.
I had this error once, too. Then I realized the provisioning profile (Project Targets -> Code Signing) was set to 'Ad-Hoc' profile instead of 'Production' profile. Setting it back to 'Production' did the trick for me.
I've got the Answer,
just upload the ipa with Application Loader 2.9.1, even thought the apple tell you that you should upload the ipa with xcode 5.1.1 or Application Load 3.0.0, but , my solution works well
download Application Loader 2.9.1 or here
The "Error description not available" sub-error message recently became "You are not authorized to use this service".
Removing the Apple ID from XCode preferences and re-adding it fixed the problem.
I'm a Chinese user and meet the same issue, I tried all these and fail:
Regenerate provisioning profile manually or via Xcode.
Use Application Loader (I didn't use 2.9.1 because I think it's a workaround).
Make sure your developer account are the same as iTunes Connect account.
Make sure bundle ID, version and build string in iTunes Connect and Xcode and the same.
Finally I googled and someone said it depends on network, so I opened VPN, and it success! I guess China's special firewall block something?
If you're in China and you've tried all the steps above, you can try to connect a VPN and upload your app. Wish it helps.
As the error says, There is problem in uploading to iTunes Store and not in code signing. Code signing step is prior to uploading to iTunes Store. Once the ipa is created successfully it should be uploaded to iTunes Store.
I faced the problem and without changing anything It successfully uploaded after some time. I guess if we are doing some operation on iTunes Connect, in my case I was removing the build which was set for TestFlight beta testing. After I perform some changes there the issue occurred.
Not the definite solution.
I had this error, and I found that it was because of the version number in my app. It had too many revision levels. You're allowed a maximum of 2. For example, 1.2.3 will pass validation, but 1.2.3.4 will generate the above error in Xcode 6.
I was getting the same error and I tried for like 15-20 times but was out of luck. Then suddenly it stuck with me what if the network is causing this. Since I was on WiFi, I sat next to the router and it worked in the first go itself. Since there is no proper message by the Apple I tried even this and it worked.
Note: If the size of the binary is quiet large then probably good internet connection is required too.
If you are in china use vpn. I fixed by use a vpn! The gfw block the upload api. you can check this.
This is also workaround but you could upload app with Xcode 5.1.1, if you still have one. Generated with Xcode 6.1 *.xcarchive files are available from older Xcode so there is no need to generate *.ipa file.
Just a tip:
Before you start to change and installing things, try to:
set the Provision profile to another one
update your Provision profiles in your account
close Xcode
open Xcode
set the Provision profile to the right one
Archive again
it worked for me!
In my case i user a wrong account with wrong password !
when i relogin, i fixed the problem, holp it will help you!
I have got this error when I tried to validate a build.
It seems just a few minutes ago I could at least validate and got a different error (with version number, I must increase it to 3.4.1 since 3.4.0 is already approved).
But it may be because I had a Pending Developer Release (v 3.4.0) . May be I have to release that version or cancel the binary. Otherwise I cannot validate the current archive.
I shall come back if that is the reason.
In my case what helped was... to wait. I had just deleted a version of the app and while itunes-connect appeared as I could upload another versione it takes some times to the servers to actually acknolegde this.
Waited until I got an email saying "App changed status to Ready for upload"
This always works for me:
Download the correct profile and certificate from member center;
Quit XCode (Not just close the project);
Try archive and validate again.
I usually get over this with a simple workaround.I get this error when I try to upload archive from Xcode 7.So I archive my project with Xcode 7 but I handle upload process from Organizer of Xcode 6.3.Xcode keep organizer content same across different versions of Xcode.
In some cases it might be a notwork/firewall issue. Make sure your the needed ports are open.
Also iTunes Connect must be working. Currently it is showing "iTunes Connect is unavailable until December 29"....
Here is a blog post about it.
On week were no one will be able to update apps. Greate...
I am trying to submit an app to the apple store via Xcode 4's in-built application loader. I created an archive, then went to itunes connect and made sure the app status is ready to upload. Then when I come to xcode and do 'Validate' or 'Submit', I just get the following message:
An error occurred talking to the iTunes Store
No details are given. Any ideas?
Update: I used the classic Application loader and submitted my app. No idea what the real issue was.
My mbp now run Xcode4.2(4D199) on Lion, I installed the latest java for Lion. And finally I sovled this issue.
Many guys said, he can used the old Application Loader app to upload the apps. so I guess the problem is the latest Application Loader app(2.4.1 (190)), and the fact told me I am right
Okie, in short words:
Here is the solution:
I hope you guys do not delete the old Xcode(4.1). We Should pick up the old version Application Loader app.
cd /Contents/Resources/Packages
cp ApplicationLoader.pkg ~/Desktop/
Now, you get the ApplicationLoader package.
Install the old one.
Tips: you can remove the latest Application Loader app in path: /Developer/Applications/Utilities/ or just remane it.
That's All.
Hope this way can help you and enjoy the new Xcode4.2. Also hope apple developer can saw this problem and test the latest Application Loader app more.
If your target has any spaces or special characters, remove them as they can sometimes cause this error.
It sounds like a connectivity or temporary network issue. I would check your network connection and try a bit later.