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.
Looks like broken deploy on Apple’s end where they accidentally rolled out an internal page to third-party developers. AppleConnect and Quip are used internally so it’s not surprising to see them mentioned. (The link that is failing to load is behind Apple’s corporate VPN.)
This happens if you are including debug information of your libraries with the project archive but are not including binaries. Open the Organizer window in Xcode Right-click on an archive that had this issue and select “Show in Finder”. Right-click on the archive file and select “Show Package Contents” In the “dSYMs” folder you will … Read more
If you don’t want to use testflight, here is another over-the-air solution: In your xcode project go to Product > Archive Click Distribute in the xcode organizer window that appears when the operation is complete Click Save for Enterprise or Ad Hoc Deployment and choose next Choose your ad hoc provisioning profile (created in the … Read more
I think this is a temporary issue from iTunes connect if you wish to remove you currunt build from App Store that appear as a waiting for review follow the following steps. with the new iTunes connect you if your app is waiting for Review state you can see this type of information in side … Read more
FYI. Apple thinks 1.11 > 1.2, so if you are going from 1.11 to 1.2 you need to go all the way to 1.20. Enjoy.
The build is not visible until the “Processing” step is in progress in the “Prerelease” tab. It should depends on the size of your app. For a 10Mb app of mine, it took about 5 min.
Basically <key>ITSAppUsesNonExemptEncryption</key><false/> stands for a Boolean value equal to NO. Update by @JosepH: This value means that the app uses no encryption, or only exempt encryption. If your app uses encryption and is not exempt, you must set this value to YES/true. It seems debatable sometimes when an app is considered to use encryption.
It’s been my experience that Xcode occasionally gets confused about which signing certificate to use. I got into the habit of quitting and restarting Xcode after any change to the code signing settings (and doing a clean build) to work around this problem.
Your live apps will not be taken down. Nothing will happen to anything that is live in the app store. Once they formally expire, the only thing that will be impacted is your ability to sign code (and thus make new builds and provide updates). Regarding your distribution certificate, once it expires, it simply disappears … Read more