I am trying to submit to iTunes Connect with Xcode 6.4. I am getting this error
Unable to Validate Your Application
The application you have selected does not exist.
I am able to find the provisioning profile through my dev account on the previous step. I have double-checked all identifiers. I tried Application Loader as well and got basically the same error. What is weird is that I submitted another app several hours before to the same account with no issues. Any help would be greatly appreciated.
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.
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.
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
Exporting and uploading via Application Loader worked for me.
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
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.
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>
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.
Related
I have created an app which has NFC tag reading functionality. I have done some changes to it and uploading the new version to App Store. Everything was working fine until last week when I updated Xcode to 11.1. Now when I Archive it I have the following error saying.
"Invalid entitlement for Core NFC framework. The sdk version "13.1" and min OS version "11.0" are not compatible for the entitlement 'com.apple.developer.nfc.readersession.formats' because TAG is missing in the entitlement.
I have done the following changes to my info.Plist file but the error still persists.
Any help will be appreciated.
Plist Changes
<key>com.apple.developer.nfc.readersession.formats</key>
<array>
<string>NDEF</string>
<string>TAG</string>
</array>
So, removing NFC tag reading from capabilities and adding it again, which added an entitlements file. This fixed the issue.
Provisioning profiles showing error after adding NFC tag-specific data protocol to entitlements which is requirement of iOS 13 and Xcode 11 for using NFC in app.
I have re-checked the profiles NFC is enabled for the bundle-id and provisioning profiles are also valid and includes NFC.
I need to upload a production build but because of this error I am not able to. Is this iOS 13 or Xcode 11 bug? What should I do for fixing this?
After a number of hit and trials, I was able to solve this issue.
Here are steps I followed:
1) In developer site, Open your app identifier, click edit, disable NFC and then re enable it.
2) Re-download the provisioning profiles and install them.
Reason behind it could be when we re-download the profiles it contained information about new NFC tag item which solves the problem.
Preeti. I have the same issue here. I started with an app that uses NFC and is built with Xcode 10.2
It is my aim to update this app to build using Xcode 11.1 However when I do so I get an error saying that have missing entitlements, I can solve this error by adding TAG to my entitlements file like this:
<plist version="1.0">
<dict>
<key>com.apple.developer.nfc.readersession.formats</key>
<array>
<string>NDEF</string>
<string>TAG</string>
</array>
</dict>
</plist>
However once you do this this is where I encounter the issue you describe, my build now complains that my provisioning profile "doesn't match the entitlements file value for the com.apple.developer.nfc.readersession.formats entitlement." Is this the same issue you are having?
This despite my profiles having previously contained the NFC tagging entitlement, and having worked fine on Xcode 10.2 Have these entitlements changed for Xcode 11 and how do we solve this and maintain backward compatibility?
Using >iOS13.0: This link gave the solution (i.e eliminate the NDEF-entry in your entitlement)
First before anyone suggests this has been answered elsewhere on SO, I submit that ALL of those answers assume you are compiling with XCode, which is not the case for me. I am using Adobe Animate to compile an Adobe AIR application and deploy to an iPad.
Updated Adobe air SDK to latest 32.0 and have tried re-creating my certificates and provisioning profile from scratch.
If I try to deploy directly from Adobe AIR I get an error message
"Application verification failed"
If instead I publish an .ipa and try and deploy via XCode I get the following
If I furthermore check entitlements on my app.bundle I see
<plist version="1.0">
<dict>
<key>application-identifier</key>
<string>foo.domain.app</string>
<key>get-task-allow</key>
<true/>
<key>aps-environment</key>
<string>development</string>
</dict>
</plist>
but checking entitlements in my Provisioning profile I see
<key>get-task-allow</key><false/>
Could this be the source of my error? If so, how do I get both these values to be the same?
Any replies welcome as I need to launch this!
Here are a few ideas/things to check.
Check beta reports key is removed from the app descriptor.
When changing iOS certificates, delete the old ones via Keychain Access, then restart the computer before creating the Certificate Signing Request for the new cert.
Check that the new assets.cer has been created for the icons and it has been included in the package.
Check that all icons are present and all casing is correct in the naming on icon files as well as in xml.(e.g. icon and Icon)
Ensure path to SDK is correct. e.g. /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS11.2.sdk
If you still cannot install the app from Animate, try including the beta reports key, publish the app and upload it to TestFlight.
When distributing an iOS app for a client using the "Enterprise Distribution" option, the app downloads and installs but then quickly disappears from the home screen. After rebooting the iOS device, it reappears.
In my situation I actually just reuse the .plist file between builds that is generated if you were to click the "Save for Enterprise Distribution" checkbox when you are about to save the .ipa file. The value I had typed in for the "bundle-identifier" key had an old APPID instead of the one the app is currently distributed under. Correcting this error and reinstalling the app from our website fixed the problem.
Essentially adding a missing .app. to our bundle-identifier allowed the application to install properly and stay on the homes creen without need for reboot.
from:
<key>metadata</key>
<dict>
<key>bundle-identifier</key>
<string>com.mycompany.MyApp</string>
to:
<key>metadata</key>
<dict>
<key>bundle-identifier</key>
<string>com.mycompany.app.MyApp</string>
#ThaDon Thanks! I upvoted you for this post. I had a similar problem. I had a plist which I reused from someone else and didn't pay careful enough attention to the value I put in for the bundle-identifier (the previous person used just the app name as the bundle identifier, but I used the recommended reverse domain notation com.. . It worked fine on iOS 6, but on iOS 5 it downloaded/installed and then disappeared, as you described. Once I put the exact same bundle identifier I had in my Xcode project, it worked the way I expected it to.
this is really puzzling me: my flash-builder 4.6 application works fine with the ad-hoc distribution profile. but when i try to submit the .ipa-file via the application-loader, i always get this error:
iPhone/iPod Touch: application executable contains unsupported architecture(s): arm
i also tried to put the armv6/armv7 keys into the infoadditions. nothing seems to help. any idea what i am doing wrong?
I was having this same problem and it turned out to be a problem with the Application Loader and Lion OS. I was able to upload the same .ipa file that had this error when I used a computer running the OSX 10.6
Take a look here: http://devgirl.org/2011/06/20/flexair-for-ios-development-process-explained/ and here: http://forums.adobe.com/message/418851
It seems that you have to add
<key>UIRequiredDeviceCapabilities</key>
<array>
<string>wifi</string>
<string>armv6</string>
<string>armv7</string>
</array>
to your <infoAdditions> tag!