application-loader

I am submitting an iOS app to the App Store using Application Loader, however, it never gets past the " Sending API usage to iTunes Connect " stage. There is no error - this stage just doesn't complete. I have verified that the Mac is connecting to the internet (I can visit websites). Also, the app is tiny (6MB) so this can't conceivably just be a long upload. I've tried leaving this for 20 minutes. The background to this is that I developed in Flash CS5 on a Windows PC, built it for distribution there, and now on the Mac I am loading the final file into Application Loader to submit it. It

I got this error from Application Loader when uploading my app to App Store. My app was developed at the time of iOS 3.0, and still targets at iOS 4.3 and above. I recently updated the app to make it iOS7-compatible. But the Application Loader always returned this type of error to me. I searched the Internet and found that I am not alone. So I created this post and hopefully what I found out about the app icons can help other people. Sounds like you may, like me, have accepted the suggestion by XCode 5.0 to migrate your icon files to a catalog. When you do that, you need to remove the

Application Loader shown me a weird warning message instead of the check-in-big-green-circle before the "Thank you" dialog. "Creating a new Signiant Transfer Engine because the previous transfer had to be canceled. This session is at risk of running out of available system resources." I used Application Loader 2.5.2 on OS X Lion 10.7.3. In the Activity window, all seemed good and the binary itself has been uploaded to the iTunes Connect, the app status goes Waiting For Review. Has anyone experienced this? philippe Same error message "Creating a new Signiant Transfer Engine because the previous

I know there are a lot of questions about this already, but I am fairly certain my question has not been answered yet. I uploaded a build of my iOS app via Application Loader, and that went well. I got to the end with a message of "Done", so I thought it was okay. Then I went to check in iTunes Connect and I cannot see a build ( not even under "Activity" ). I waited for an hour and I retried uploading the build. In Application Loader I now get the error "Redundant Binary Upload", so that tells me that my build is somewhere in iTunes Connect, but I can't find it. What could have gone wrong? Is

I recently re-signed my app with another certificate (I do not have the source code, so I had to do this to upload it to the App Store). When I tried to upload it, I got: ERROR ITMS-9000: "Missing Code Signing Entitlements. No entitlements found in bundle 'xxx.xxxxxx.xxxxxx' for executable 'Payload/xxxxxxx.app/Xxxxxxxx'."" at SoftwareAssets/SoftwareAsset (MZItmspSoftwareAssetPackage)". I read in other posts that my bundle ID has to match my new App ID, from the new certificate I just signed. I need direct instructions on how change the bundle ID in the IPA file! Like, real step-by-step

I am trying to upload my app but I get this error when I try to upload it through Application Loader: A new version of the iOS Paid Applications Agreement with updated pricing information is now available in the Contracts, Tax, and Banking module. To be able to continue creating new apps and upload binaries for the App Store, your Team Agent must review and agree to the updated terms of the iOS Paid Applications Agreement. To access the iOS Paid Applications Agreement, you must have accepted the latest version of the iOS Developer Program Agreement in the iOS Dev Center on developer.apple.com.

I know how to sign an app with Appstore mobile provision, and how to re-sign an Adhoc-signed IPA with Appstore mobile provision. This is not my question. My question is, can you submit Adhoc-signed IPA to Appstore / iTunesConnect, and have it pass Apple verification and eventually be distributed through Appstore. Why? So that I don't have to store a redundant Appstore-signed IPA along every Adhoc-signed release candidate IPA, and don't have to do the extra step of re-signing that requires a Mac machine. When using Application Loader , it is able to find all the stupid little errors, like