Since the release of iOS 8 on the 17th, all my development and deployment profiles are showing as invalid in the Apple dev center. Also none of my apps using iCloud will run in either Xcode 5.1 or 6 GM on an actual device. Get a message stating entitlements do not match provisioning profile. The only acceptable iCloud containers now have to start with iCloud which do not recognize data already stored in iCloud using the previously require iCloud container naming structure.
Any solutions? I've searched the web and Apple dev site for hours with no solutions found. I can't be the only one having this problem. Very frustrating after just releasing an App on the App Store and now can't change any code to update it!
Click on Use Default Container
Click on Specify Custom Containers
Reselect your custom containers
Not sure this is the final answer, but I finally found a way to access the old iCloud information in my app on a device. I returned to Xcode 5.1.1, deleted the entitlements file in my project. Edited both the Development and Distribution profiles on iTunesConnect (using iCloud.xxxx settings that are only allowed now), downloaded and installed in Xcode 5.1.1. I checked the Key-Value Store: under iCloud capabilities and clicked the + under Ubiquity Containers and made sure the targets all had the same container (com.companyName.AppName) for each target in the app. Then attached an iOS device and ran the app. Errors appeared, returned to each target and clicked "fix" under Capabilities - iCloud. Had to click fix several times until no longer appeared. Then ran the app again, the previous iCloud data stored in the app before iOS 8 release showed up in the app and all appears to work.
The above resulted in a separate entitlements file for each target, previously there was only one entitlements file used by all targets.
I have not tried with with Xcode 6 again yet, but I finally have access to my app through Xcode 5.1.1 and can work the fixes and enhancements for my published app again.
Update (11/5/2014): Was able to upload to app store for beta testing without problems using Xcode 5 with the above method.
Hope this helps someone else.
Related
After experimenting a bit with SwiftUI making a new iOS app; I just got to the point where I want to put it on TestFlight to start testing with more people.
But this is where I am hitting a new problem.
After archiving, here is what I get when trying to upload the archive to iTunes Connect:
Provisioning profile failed qualification
Profile doesn't match the entitlements file's values for the application-identifier and keychain-access-groups entitlements.
As far as I can tell, I am not doing anything more or less than I always did in the past, when uploading a new app.
Here is what I can say about the app:
It is using SwiftUI. (This is the first time I upload a SwiftUI app, if that ever matters here)
It is using Core Data.
It is using MapKit.
It is using location triggered notifications.
For the environment:
I just upgraded Xcode to version 11.6 (11E708)
I am using Mac OS Catalina version 10.15.6.
Is there anyone who has faced the same situation before?
Or is there something to check knowing the information above?
I'm having the same problem since around July.
Here is what worked for me.
Archive the project on Xcode11,
Open the Organizer window on Xcode12 Beta
And as usual, you can try uploading from there,
BUT in my case, Here, I faced another issue saying failed to 'APP STORE connect operation error'.
If you face this same error like this, then here are other steps you should take.
Download 'transporter' from the Mac app store.
on the Xcode 12 Beta organizer window, instead of uploading the app, click export the app.
Then open the transporter, and add the file you just exported, then you will see 'Deliver' button. After clicking it , in my case, the app was uploaded in a couple of minutes.
Hope it works for you too.
Xcode11: Version 11.5 (for archive)
Xcode12: Version 12.0 beta (for exporting a project on organizer)
My Mac: macOS Big Sur Version 11.0 Beta
The problem is because you need to check the capabilities. The capabilities in the project needs to be equal to which you configurated in the section of "Certificates, Identifiers & Profiles" in the app. In this question you can find more info
After installing 11.1 I created a new project, removed the multi-window stuff that Xcode now gives you by default, and started developing a test app that uses Vision Framework.
By the time I got to the point where I needed to test on the device instead of the simulator, I was struggling to make my app work correctly. I finally realized that running the app on my phone required me to delete the app and run a fresh install or the changes wouldn't be pushed to the device. This continues to be a problem. Even a new print statement won't be shown in the debugger output unless I go through the rigamarole of deleting the app and running fresh. Subsequent changes still use the initially installed build regardless of the number of times I clean/build/run.
I've cleaned the project, build folder, derived data, Xcode cache, rebooted my Mac, rebooted my phone, reinstalled Xcode, obliterated and reinstalled Xcode again, all with no success.
Anyone else with this issue? What am I missing?!
Ok, after two days of trying to fix this, it turns out to be some kind of Apple bug on iOS 13 (surprise, surprise).
Here's what I did/found:
I tried running on another device and was able to see changes on subsequent runs.
Back on the original test device, the issue still exists (Xcode issue ruled out)
I had a couple other test apps that were signed with the same development cert on the device, so I deleted those too.
Running the app from Xcode again prompted me to go to settings to trust the developer certificate
Changes and updates are now pushed to the device on each run from Xcode.
TLDR:
If you happen to run into a similar issue, try deleting other development certificate apps you have on your device and re-trust the certificate.
We've been developing and testing a Watchkit Extension app (iOS 12.1 and WatchOS 5.1) for the past few months and successfully testing it on a simulator and local, connected devices (iPhoneX + Watch 4) using xCode 10.1.
This past week we built an archive for posting to App Store Connect. We got stuck in the Archive Organizer after archiving for release. The "Validate Content" button was disabled, the Version is blank, the Identifier is blank, and the Type is "Generic Xcode Archive". Unfortunately, all we can do is export the .app files from the Archive Organizer; we can't push the archive to App Store Connect.
We made sure the build scheme was set to Release and we archived to a Generic iOS and WatchOS device. We also set Skip Install for the three targets (iOS app, Watch app, Watch extension) to No as we assumed none of those are static libraries. We even tried every permutation of Skip Install settings. We looked at the issue in the following link and we have no Header steps in the Build Phases of any targets:
https://developer.apple.com/library/archive/technotes/tn2215/_index.html#//apple_ref/doc/uid/DTS40011221-CH1-PROJ
We have two frameworks we included in the project using carthage. We thought maybe these were causing issues, but we rolled back to a branch before we added them and still have the same problem.
We made sure the build in the Scheme is set to a single target and cleared out the Derived Data folder. Still no dice.
I’m not 100% sure from your question, but are you trying to push an archive of the watch app to the App Store?
If so, that’s not how you submit the app. The Watch app is embedded in the “regular” iOS app, and to distribute it you need to archive and submit that app as usual.
If I’ve misunderstood, feel free to ignore this!
I had the exact same problem. When I changed Skip install on the watch app and watch app extension to YES, it suddenly worked. No idea why.
I downloaded Xcode 7.1 from the App Store today after working from 7.1 beta downloads from developer.apple.com and have a new iOS app build to upload. So I did:
Product > Archive
Upload to App Store (or Validate)
But the response was:
You are not authorised to use this service
Intriguingly, when I 'Export' the build to the Desktop and then use Application Loader 3, it uploads without error.
Is this an iTunes Connect bug? Or is there a new Xcode checkbox I've missed?
Note: I've also tried removing and re-adding my AppleID as suggested here, and restarted my Mac for good measure (which actually allowed the validation to work once), but still no luck uploading directly from Xcode > Organiser.
I met the same issue today and I think it is a bug of Xcode 7.1
Finally I managed to submit my app via Application Loader. There were warnings but it did work.
Here are the basic steps:
Archive
Export
Xcode menu --> Xcode --> Open Developer Tool -->
Application Loader
Double click "Deliver Your App" and choose the
file exported in step #2
click next and follow the instructions until
the end
Here's the quick solution:
Don't use Xcode beta versions to submit apps for release — it's beta for a reason and shouldn't be used with production code.
Submitting Apps
Apps that are created using beta versions of Xcode or that are built
for beta versions of operating systems will not be accepted on the App
Store and Mac App Store. Apps that you submit should be developed
using the latest version of Xcode from the Mac App Store and should be
built for publicly available versions of iOS, OS X, and watchOS —
except when GM seeds are available. When a GM Seed of Xcode becomes
available, use it to develop your app for submission. When GM seeds of
iOS, OS X, or watchOS become available, build your app for these
versions.
↳ https://developer.apple.com/support/pre-release-software/
Having the same problems as all of you, just thought I'd share that I found a way to Validate successfully, you have to disable the "Include bitcode" checkbox before moving forward. As for the actual upload to App Store, no work around for that one other than use the Application Loader...
Also I've been seeing this too since XCode 6.4, but it seems once the current version has a couple of months after it's originally released it starts working again... fingers crossed that it starts working again soon, because uploading straight from Organizer is so much better. (I saw the Beta Version post, when I say after a couple of months for current version I'm not talking about Beta versions, just in case ;) )
Same problem here.
Downloaded Xcode 7.1 from the App Store and it refuses to upload a new version.
Happily Application Loader worked ;)
Hopefully this gets fixed quickly.
One possible reason for the issue could be multiple development accounts under one name (personal and company). I've read elsewhere (apple radar) that that caused earlier problems of this kind.
Happens here if the dev account is only admin. I had to use the central account for uploading our apps. I think this problem startet sometime with XCode 6. Didnt investigate further though since Application Loader works in cases when I dont have access to the central account.
I also have the same problem today.
Finally, I used the application loader to upload successfully,too.
Theres a few solutions I have come across to solve this issue.
Most common being to remove and re-add your developer account.
This won't work on its own though, you need to also 'view details' on your account and have Xcode download your provisioning profiles again.
The other alternative is to upload your build using application loader. The disadvantage to using this solution is that should you be trying to upload using a beta build of Xcode or OSX you won't be able to change your apps .plist in the archive folder to trick iTunes connect into accepting it. In this instance all you have access to is your ipa.
Disable the "Include bitcode" checkbox worked for me.
I have a WatchKit app that runs fine in the Simulator. But when I try to run it on an actual device it never finishes installing and never provides any error message or feedback.
The iOS app installs and runs fine. I bring up the Apple Watch app on the iPhone and it lists the app and shows the correct icon. Selecting that, the "Show App on Apple Watch" switch is on. Underneath it it says, "Installing...". And it stays there.
I can also see the app icon on the Apple Watch. Selecting it just shows the spinning wheel indicator as if it is trying to load.
Things I've tried based on other suggestions I've found here, on the Apple Developer forums, and around the web:
Verified that all app bundle IDs are correct and match.
Verified that the deployment target is iOS 8.2.
Verified that the WatchKit App runs in the simulator.
Verified that my provisioning profile includes my Apple Watch's UDID.
Verified that my Apple Watch shows up as a "Paired Watch" in Devices.
Deleted the app from my phone, and then rebooted my phone, watch, and Macbook before reinstalling.
None of the above work. Any suggestions?
Thanks!
Thomas Aylesworth
A friend who works on the USA Today iOS team, including the Apple Watch app, suggested I go to the project settings for the WatchKit App target and set "Skip Install" to NO. Sure enough, after doing this, I was able to install.
I've found it very useful for reading the iPhone console log. (Not to be confused with crash logs).
Use Xcode --> Window --> Devices -- select your plugged in iPhone, and make sure the log screen lower left arrow is down.
In my case, I had invalid provisioning profile entitlements, which were corrected via the Apple Dev portal, and re-downloading the profiles -- after making sure the entitlements were correctly being set in the WatchKit App Capabilities.
Check Info.plist file. In my experience if there is something added there that is not supposed to be there, it will cause this behavior. I added NSLocationWhenInUseUsageDescription and it caused this same issue.
I have found a similar problem due to my storyboard referencing an image which I later deleted (I no longer actually used it anymore). This gave the symptom of running ok on simulator but not deploying fully on hardware as you are seeing. To exclude this potential problem go through each image view on your apple watch storyboard and look out for the exclamation mark against image view entries.
I had the same problem but for me it actually turned out that the Apple Watch was running a WatchOS version lower than what what I had in XCode. I could not see a runtime warning about this (it just silently failed), but when selecting WatchKit scheme in XCode with device connected there was a small warning about version requirement.
You can also try deleting the watch app on the watch by long tapping on the icon and then you should get the giggle UI with a X on 3rd party apps. You can then delete the watch app and retry the install.
I was getting this error too, and I got it to install, after creating a new project from scratch in the non-beta Xcode, and copying my assets and code into the new project. I had the same problem, and tried everything that people suggested on other posts, without any success, including everything that you listed above.
Apparently, there was something incompatible with the way the project was stored in the beta Xcode, that I had created for the WatchKit app.
Here's what works for me with iOS 8.3 and Watch OS 1.0.1:
Make sure your app is finished installing on your iPhone.
Restart the iPhone by holding down the Home button and Wake/Sleep buttons.
Launch the TestFlight app on your iPhone.
Staying in TestFlight, go to your app's detail page and toggle the Install on Apple Watch to the On position.
Press the Home button on your iPhone to exit the TestFlight app.
Press the digital crown on the Watch to get to the Home screen. An icon for your Watch app should appear and begin installing.
make sure your app support 64Bit, otherwise it cannot run on Watch,just spinning there.
Did you add a custom entry to the of your Info.plist of the WatchKit App
This isn't allowed and it will fail validation and will just sit on Install...
Checkout the device console log for information on it
Yeah, had that problem too.
I deleted the Xcode Beta (and the .dmg) downloaded it again and installed it.
Don't have that problem anymore.
In my case, I disconnect the iPhone and the Mac, reconnect them via data line. Then something appear on my watch, a choice, agree or disagree, agree it. After that, Xcode begin to install symbols for watchOS 2.1:
When this is done, you can check it in Library->Developer->Xcode->watchOS DeviceSupport->Watch1,1 2.1 (13S661)->Symbols
Then I disconnect the watch and iPhone, reconnect it. Now I can install WatchKit App on my watch.
I have followed the answer by #hunterleebrown to see the log and found that the WatchOS version is not updated (i.e. Watch OS version is lower than the required version).
Here is the screenshot [ The log says (4th line): The system version is lower than the minimum OS version specified for bundle at ... ...]:
Then I went to the iPhone's watch app's-->general settings-->Software Update and found the watch OS is not updated (which is obvious). Then I downloaded the update and installed it. Then it worked!
Note: I also tried quitting XCode, restarting iPhone and Watch but didn't work for me.
Press "Trust this device on Apple Watch"
I had the same endless installation issue ending with a Time Out error and I finally fixed it thanks to this answer: https://stackoverflow.com/a/61636074/2854405
I had to:
Unpair my iPhone (from the "Devices and Simulators" screen),
Exit Xcode
Replug my iPhone
Trust the iPhone again when it was prompted
Start Xcode
Rebuild
I also had the same issue.
#SwampThingTom suggestion is good, but it changes the archive format as well size increases too.
In my case, the issue was DER entitlements not working only watch app, mobile app was fine.
Make the changes as per the comment over here This Code Signature is no longer supported when building app on iPhone 12
Upgrade to Xcode 13.1
In my case I resolved this problem when selecting the WatchApp target to creating AdHoc.
So, for example, there is three targets in project:
Demo;
Demo WatchKit App;
Demo WatchKit Extension;
If create AdHoc with Demo target, you will get infinite installation.
If create AdHoc with Demo WatchKit App target, the problem goes away.