Xcode 6.4您选择的应用程序不存在

小开

Exporting and uploading via Application Loader worked for me.

小开

I tried Application Loader and it worked. It did not work 2 hours earlier. What is weird is that I tried to download an app from the App Store and they could not find my account. Some new terms of service popped up and I agreed. After that I was then able to download with the previous "non-existent" account. That's when I tried App Loader and it worked. Must be something on Apple's side that will be fixed shortly.

小开

Download Xcode 7 and try to upload new build make sure that you changed version or (and) build number of app, it should work.

小开

It seems to be a bug/"feature" of iTC not related to Xcode version. Bundled frameworks should bump their versions(CFBundleShortVersionString) to match the version of the app. Related topics: https://github.com/CocoaPods/CocoaPods/issues/4421 https://github.com/Carthage/Carthage/issues/859

小开

Failed to upload archive using Xcode 6.4 and 7.1, but successfully uploaded with Xcode 7.0.1. http://adcdownload.apple.com/Developer_Tools/Xcode_7.0.1/Xcode_7.0.1.dmg

小开

I was having the same issue, here's what I did to send the app to the app store:

On XCODE create generate the "Archive", once you get the "Organizer" window/popup, validate it as you normally do. If validated, then click "Export" and select "Save for iOS app store deployment". Save it somewhere and take note of this location, you'll need the IPA file.

Install the "Application Loader" from https://itunesconnect.apple.com/apploader/ApplicationLoader_3.1.dmg, if you don't have it already.

Follow the easy steps to push the app to the app store. That is "Deliver your app", select the IPA file and that's it!

小开

While other are having success with Application Loader, I did not and received a different error « You are not authorized to use this service » Great!

Since iOS 9.1 was just released yesterday perhaps Xcode 6.x is being phased out, but we're not ready to migrate to Xcode 7.x for this particular project.

I was successful by archiving in Xcode 6.x and using the Organizer in Xcode 7.1 to submit to the App Store. The procedure is as follows:

Rename Xcode 6.x (In my case Xcode632.app).
Download and install Xcode 7.1 from .dmg file, not as an upgrade.
Build and archive your app in Xcode 6.x
Close Xcode 6.x
Launch Xcode 7.1 but do not open your project.
In Xcode 7 Select Window->Organizer.
Submit to App Store.

Hopefully this helps you if both the Xcode and Application Loader uploads fail.

小开

It looks like this can be caused by some new version number validation logic on Apple's end. In our case, tacking an extra ".1" onto the end of the version number strings for the app allowed it to be uploaded with Application Loader.

Really weird/deceptive that the error message for this would be "The application you have selected does not exist", though.

小开

I was having the same issue. I tried to upload with Application loader then got descriptive errors about the bundle version. After removing all third party info.plist from pods and static libs, will work to upload my build.

小开

I fixed this issue. I had to update my OSX to 10.10.5 and XCode to 7.0.1. In XCode you need to set few keys. NSAppTransportSecurity Key is required if your app or game needs internet access. After this setup it works perfectly from xcode it self. And no issue on live itunes connect.

<key>UIRequiresFullScreen</key>
<true/>


<key>NSAppTransportSecurity</key>
<dict>
<key>NSAllowsArbitraryLoads</key>
<false/>
<key>NSExceptionDomains</key>
<dict>
<key>domain.com</key>
<dict>
<key>NSExceptionAllowsInsecureHTTPLoads</key>
<true/>
<key>NSExceptionMinimumTLSVersion</key>
<string>TLSv1.1</string>
<key>NSExceptionRequiresForwardSecrecy</key>
<false/>
<key>NSIncludesSubdomains</key>
<false/>
<key>NSThirdPartyExceptionAllowsInsecureHTTPLoads</key>
<false/>
<key>NSThirdPartyExceptionMinimumTLSVersion</key>
<string>TLSv1.1</string>
<key>NSThirdPartyExceptionRequiresForwardSecrecy</key>
<false/>
</dict>
</dict>
</dict>

小开

UPDATE: It appears that Apple has remedied this bug. I just successfully uploaded a build using Xcode 6.4 to iTunes Connect. I believe this was either an organizer bug or an iTC bug but they've fixed it.

Before the solution was to use application loader.

You should be able to submit using Xcode 6.x now. We need to upload build from 6.x still because Xcode 7 requires a lot of refactoring due to ATS. The standard "AllowArbitraryLoads" doesn't cut it for my project.

小开

My solution for similar problems is use of Fastlane Tools https://fastlane.tools
First You can use GYM tool for build/archive your project, and then Pilot for send it to iTunesConnect Testflight. This tool fixes all of my problems with Code signing, submitting, etc. so I can recommend it.