I am trying to submit my app to iTunesConnect from yesterday to now but, still not successful on that.
When I am trying to submit the app over Xcode, on uploading archive step after a few seconds it says "iTunes Store Operation Failed" with "No Error description".
When I am trying to upload by Application Loader it says "Application Loader is currently unavailable, We are having trouble to connect App Store. Please try again later." again with "Error description not available".
I know yesterday iTunesConnect was in maintenance but I cannot figure out why I still cannot upload the archive yet. Is anybody else dealing with an error like that? Or have an idea why this error happens?
Thanks in advance.
After renewing the distribution profile and some re-setting on code-signings, now, I am able to send archive to App Store.
Related
I have submitted an iOS application to iTunes connect and it is in beta testing state. I have added a new external tester to the account and the new tester got the notification from iTunes connect. But the user is not able to install the application, getting an error message as below,
The invitation is invalid. Try again. If the problem persists,
contact the inviter.
Can anyone please help me?
Thanks guys,
This was an iTunes Connect error. After a couple of hours the problem got solved automatically.
In our ipad application user has to enter his details for registration. After user enter his details we save those details in the Device's keychain. So next time user launched the app user can use the app without registering again. Since we save it in the keychain even the app reinstall by deleting is also works fine.
To write to key chain we use sskeychain class as most developer do. This feature is working properly in devices without any issue.
One of our client use their symantec (unitymobile) mdm to distribute this app to their users. But when user install it through the mdm app gives following error when saving data to the key chain.
"The operation couldn’t be completed. (com.samsoffes.sskeychain error
-34018.)"
Initially we thought this is due to one of the policies they have included. But no luck. Can some one please tell me what has happened here and how to solve this issue.
P.S.
Actually underlying error was this.
(OSStatus error -34018 - client has neither application-identifier nor keychain-access-groups entitlements)
I try to upload my game developed with Starling to the appstore but the "Application loader" stuck on "Sending API usage to iTunes Connect", 10 days ago the upload was successful, the new version have only a different line of code then the way to compile is same.
Somebody have this problem?
Somebody have a solution?
I try with this but no work for me:
Can't Submit App to App Store: "Sending API Usage to iTunes Connect" either times out or loses connection
Application Loader (Apple) stuck on "Sending API usage to iTunes Connect"
This is common issue for most of the developer. You may go with Application loader to upload build or you need to restart your wifi or mac. and then it will work. I faced this issue many times there is no specific reason for this.
I've searched a lot for this but I couldn't find the right answer.
I want to log in on the iTunes Connect Mobile app, but if I try to log in to the app, there comes an alert which says:
"Authentication Error"
"No data found for your request (206)"
I really have to use the app, but this error blocks me. Is there a solution?
Is it a bug in iTC mobile or is my account the problem??
It happened with me also, then realized Apple is doing a maintenance upgrade so no data is available to end users during that time.
I am trying to submit my first application to the Mac App Store. I have setup the signing certificates on my computer, as well as setting up the application in iTunes connect. Xcode allows me to produce an archive of my app, and even export a signed pkg file. Both Application Loader and Xcode say that my binary passes "validation", but shortly after uploading my app to iTunes connect it is reported to have an "Invalid Binary." I read on Apple's iTunes Approval Process page some reasons why this might happen:
Appears when a binary is received through Application Loader, has been processed, but your binary is invalid. Examples of an invalid binary are: your binary icon does not meet our requirements, you have placed the payload directory at the wrong level in the .app wrapper, you attempted to use a non-increasing CFBundleVersion, etc.
Unfortunately I am not receiving an email when this error occurs, and nothing is telling me what the problem is. I am kind of hoping that Xcode would tell me if I signed my binary wrong in the "Validate" stage, but I may be wrong.
My question here is: why might iTunes connect be reporting an "Invalid Binary" and how on earth can I fix it?
EDIT: I have taken some screenshots of my project's configuration settings, and of iTunes connect:
iTunes connect app page
Application in the Archive list
Entitlements plist
Code signing settings
Info.plist
Build settings (architectures, etc).
You most likely are trying to submit a build that has the same version number as an earlier build. All builds that you upload to iTunes connect must have different version numbers. For example: Joe submits his first build of his app to iTunes connect as version 1.0, next time he submits he must change the version to 1.1 or any other higher value.