I've downloaded the CloudKitAtlas sample code from Apple dated Sept 8. I did:
Setup the App ID
Enable the iCloud in Xcode capability
Setup the provisioning profile
Login to my iCloud Account in my Simulator (the different account from my developer account).
But the app crashes when I click the Discoverability in application. The error message is:
An error occured in requestDiscoverabilityPermission:: CKError
0x7fd7f162c1c0: "Not Authenticated" (9/1004); "Account couldn't get
container scoped user id, no underlying error received"; Retry after
3.0 seconds>
Do I miss anything setting up the iCloud? Thanks
I had the same problem on my app. Deleting the application from the simulator and restarting it fixed the problem. Take a clean build if necessary
Also, make sure that you are logged in to iCloud in Settings app.
Related
A year ago I worked on an Iconic/Cordova app and I helped build the iOS side of things. I have a MacBook Pro and an iPhone so I was setup to test the iPhone app, whereas another developer had a Windows machine and an Android phone, so they focused on testing that side of things.
We were working for an entrepreneur who had created an account in the Apple developer portal. Though he added my developer account to his "team" in the Apple developer portal, I was never able to make that work, so I simply started using his credentials:
cap55#cornell.edu
Now I am working for a different company. I am working on a React Native app.
Oddly, when I try to build the iOS part of this in Xcode, I get this error:
Code Signing Error: The operation couldn’t be completed. Unable to log in with account 'cap55#cornell.edu'. An unexpected failure occurred while logging in (Underlying error code 1100).
I tried several times to specify my personal account, but nothing seemed to work, so I opened up the Preferences of Xcode and I deleted the old 'cap55#cornell.edu' account.
Just to emphasize this: if I open Xcode, and then Preferences, and then Accounts, there is only one account, and that is my personal one. There is no record of 'cap55#cornell.edu' anywhere.
I restarted Xcode.
Then I tried to build again. And again I get:
Code Signing Error: The operation couldn’t be completed. Unable to log in with account 'cap55#cornell.edu'. An unexpected failure occurred while logging in (Underlying error code 1100).
It seems like Xcode is hiding this account somewhere that I can not delete? Where should I look. I want to eliminate this account.
I opened the KeyChain app and deleted almost everything in there. Then I restarted Xcode. The problem now seems to be solved.
Check your target's build settings to see what team the "Signging" section is set to. Both in General and also in the "Build Settings" tab for the targert.
I'm trying to upload my app to iTunes Connect with Xcode. I chose product > archive, choose my account, it compiles and when I try to upload it hand for a long time on:
Uploading Archive
Sending API usage to iTunes Connect...
Then it shows an error message:
I've restarted Xcode and the entire machine but still it keeps repeating itself.
What's wrong here?
This usually happens to me when the phone is connected while uploading the archive, and removing the phone so far has been solving the issue for me.
My solution was to install Application Loader. At first it seemed like it's stuck as well, but after about 10 minutes it started uploading.
I solved this issue.
There is a checkbox "include bitcode" at the bottom of the Summary screen (when you validate Archive) or Send XXX to Apple screen (when you upload to App Store) where the Organizer show the Binary and Entitlements together with Provisioning Profile. In XCode 7 it is checked by default. I unchecked it and re-run Validation - worked fine. As soon as checked the checkbox back on, it started failing with same error.
I have also unchecked the other checkbox on the same screen - symbolis upload.
Successfully uploaded the binary using the Organizr just now.
Here the solution that helped in Xcode 8, summary screen:
Still getting the same error despite "unchecking" bitcode and also archiving with the bitcode under Basic Profile turned off in the info.plist.
It would only work if I used Application Loader, like this:
First, export the application Archive from Xcode's Organizer window (it saves this into a directory on the Desktop).
Then, from Xcode:
Xcode > Open Developer Tool > Application Loader
My guess is that there is a bug somewhere either with iTunes Connect back end or xCode itself.
A couple of Xcode restart didn't resolve the issue but Application Loader solved it for the very first attempt. Also, Application Loader, is more descriptive for letting one know what's going on during the whole upload process. Plus simultaneous apps upload is possible via Application Loader.
I got this error when trying to upload an app to App Store Connect (01/20/2020). Restarting Xcode fixed the issue for me.
I've had the same issue.
Tried to upload the app with Transporter with no success.
Restarting of Mac and Xcode didn't help.
Solution was to logout from Xcode and log in back
Xcode -> Preferences -> Accounts -> Select your Apple ID and click on "-" below
To submit to App Store use Application Loader but after creating the "App-Specific" password as the following:
Log in to https://appleid.apple.com and enter your 2FA (TWO-FACTOR AUTHENTICATION) code.
Then in the Security section on the bottom right area, you'll see: APP-SPECIFIC PASSWORDS.
Generate Password... Click the link to create an app-specific password, Enter your password.
Copy the app-specific password. Enter the password into the Application Loader.
Choose the exported ipa to submit it.
For developers uploading apps with Xcode: simply change network and restart your Mac.
I solved this issue with Transporter, native Apple application. You can download it from AppStore.
https://apps.apple.com/ua/app/transporter/id1450874784?mt=12
This application has a much more information about uploading process and possible errors.
Install the "Transporter" app from the MacOS app store.
From Xcode's organizer, select your archive and press "Distribute App"
Select "Export" and proceed as usual.
Choose the exported .ipa file into the transporter and press "Deliver".
I was getting the same error. Application Loader didn't work. I couldn't open any Apple Developer/Forum webpages either to find an answer there. And iTunesConnect wouldn't let me log in. I thought the site was down and I couldn't even access the Apple Status pages.
My VPN was connecting outside the US. After turning off the VPN everything returned to normal. I have been letting the VPN connect to random places around the globe, probably should keep it in my area.
In my case, The build with the same number (e.g. Version 1.0(1.6)) was already been uploaded to AppStore. I found that after logging into itunes and checked the TESTFLIGHT BUILDS -> iOS and there I saw 1.6 (Processing)
Note: 1.0 is the version number and 1.6 is build number.
I am using Xcode 7.2 and I am not able to submit my app due to a strange error: "iTunes Store operation failed". I've reset my certificates, reset my provisioning profiles, cleared out my keychain, and still no success. I've also gone to "Xcode -> Preferences -> Accounts" and deleted my account, and re-added my account. I then went into "View Details" and clicked "Download All". I've done research which all tell me to do the steps above, but I tried all these steps countless of times and I cannot seem to figure this out.
Any ideas?
Go to member center -> Choose iOS Provisioning Profiles (Distribution) -> edit - > add file "keychain access CertificateSigningRequest.certSigningRequest " from your device -->download provisioning profile certificate and add it to keychain access --> Quit Xcode and reopen hope it will work
Did you try unchecking the Include bitcode option before sending your app to Apple? I have been getting the same error quite frequently and what I notice is that it could do something with internet connectivity. When I submit my app from office with high speed connection, there is no problem at all. But from home where I have lot lower speed, I have to uncheck Include bitcode to successfully submit my app.
The only way I was able to upload my project to the app store was to use the Application Loader built into Xcode. I believe that this is a new bug with Xcode 7.2. Here is a detailed walkthrough of using Application Loader:
When I ran into this issue, my first thought was to search Stack Overflow for solution. I did the search, found several topics. But, unlike my issue, those posters got some clue from the error such as,
App Store error: The binary you uploaded was invalid
Invalid iPhone Application Binary
Uploading Binary iPhone App "The signature was invalid" again again and again
The binary you uploaded was invalid. The signature was invalid, or it was not signed with an Apple submission certificate
Or this one:
"The binary you uploaded was invalid. the file was not a valid zip file" Error message uploading app to iTunes Connect
The binary you upload was invalid. the file was not a valid zip file
Or this one
CFBundleVersion in the Info.plist Upload Error
The binary you uploaded was invalid. The key CFBundleVersion in the Info.plist file must contain a higher version than that of the previously uploaded version.
But for me, I got nothing, it just says ERROR ITMS-9000: "The binary you uploaded was invalid"
I try to resolve this issue by the following attempts, all of them failed
Test on simulator make sure the app works ... Check!
Test on device (iPhone 5S, iOS 7 and iPhone 4s iOS 6) to make sure the app works ... Check!
Clean and build ... Done!
Make sure that I'm using distribution profile (not ad hoc, dev) ... Check!
Redo the whole process of certificate and provisioning profile ... Done!
Check my code signing identity ... Check!
Check bundle id, there are matches (Xcode == App ID in Apple Developer == App in iTunes Connect) ... Check!
App ID case sensitive check .... Check! (lower case, com.companyname.productname)
Delete target in project and then create a new one (I have one project, multiple targets) ... Done!
Delete scheme and then create new one ... Done!
Check icon size, check loading image size, check pixels per inch ... Check!
Check Localizable.strings for typo ... Check!
Delete build foler ... Done!
Restart Xcode, restart computer ... Done!
Connect to another wifi router ... Done!
Submit from my colleague Macbook ... Done!
Create new App ID, new certificate, new provisioning profile and update iTunes Connect Bundle ID ... Done!
Take a break for an hour, try again ... Done!
I really have no idea what did I do wrong. I've been submit app since iOS 4, hundreds of updates. But never ran into anything like this. In fact, I've just update another app yesterday which share the same codebase with this one, no issue at all.
Is there a way I can gather more information about "the invalid binary" Xcode is telling me? Or is there anything else I should try?
For everyone who found this topic (18 July 2014), maybe your best shot might be, taking a break for few hours (or a day) and try again.
--- Last Update ---
It turns out to be Apple Server issue
Says, I have an application called "Sample App"
This app has an app id of com.tartw45.sampleapp
This app use an App Store Distribution profile called "Simple App App Store Distribution Profile"
Back to last Friday (18 July 2014), everything seems ok, no indicator of any error but I couldn't publish the app as I stated above
Today (21 July 2014), I tried again with archive from last week, still no success.
I decide to redo the archive process and I found that "Simple App App Store Distribution Profile" is no longer valid
I login to developer.apple.com and found that "Simple App App Store Distribution Profile" also no longer there in the list of all provisioning profile. **
Then I try to create a new provisioning profile with the same name (Simple App App Store Distribution Profile) but there is an error says that this profile is already exist, please choose another name **
So, I create a new provisioning profile with slightly different name, refresh the provisioning profile in XCode, archive again and then publish .... Works!
So, It's definitely Apple Server issue and your provisioning profile (**), it has nothing to do with your XCode version or project setting (if you successfully submitted your app once before running into this issue with no reason). So, anyone who found this topic, please try to validate your provisioning profile and try to publish again.
I was having the same issue since last night and finally got it to work just now. Had to go through this process
Logged in on https://developer.apple.com> > Certificates, Identifiers & Profiles > Provisioning Profiles and revoked my company's Distribution Certificate.
Then Xcode > Preferences > Accounts > Apple IDs > (my company) > View Details and refreshed the certificates and Provisioning Profiles. It prompted that no Distribution Certificate was found on the Developer Profile and offered to request one on my behalf, which it did.
Launched Keychain Access > Certificates and removed all of the expired Certificates (somehow I had a few of them)
I went back to https://developer.apple.com> > Certificates, Identifiers & Profiles > Provisioning Profiles and edited all of my manually managed Provisioning Profiles (Development — which had to be re-generated — and Distribution — which had to be linked to the newly created Distribution Certificate and generated again)
Once again Xcode > Preferences > Accounts > Apple IDs > (my company) > View Details and refreshed the certificates and Provisioning Profiles.
Credit to Rodrigo on the apple dev forums
iTunes connect (or at least some services that iTunes Connect uses) are down for the moment, so "Take a break for an hour, try again ..." is your best shot. Apple of course doesn't update their status page until tomorrow or so.
https://developer.apple.com/system-status/
It's on Apple's side. I tried to validate a couple of apps that worked last night, no changes in code, credentials, or Xcode and this is what I get.
We found it wasn't necessary to revoke anything- when I went to Provisioning Profiles->Distribution, the two profiles for our two apps we were trying to release had been removed. I recreated those profiles (but I had to assign new names, using the old name led to a "profile already exists" message- so those identifiers are still out there- somewhere). Downloaded and installed the new profiles, resubmitted the archives we made on 7/18/14, and everything sailed right through.
Apple iTunes' Connect server is down at the moment. I have tried almost everything, but all failed.
I suggest as above to take some rest and try upload after an hour or so.
I ran into the same error when I tried validating my app. I got a message saying,
Unable to process app at this time due to general error
I searched on SO for this and only found a suggestion to wait for some time, as this is an error from Apple's servers. I tried all sorts of things, from playing with provisioning profiles to improving app performance and linking libraries, none of which resolved the issue. Unfortunately, I guess we don't have any other options than to wait and let Apple do its work.
Yesterday, I had to regenerate an expired distribution certificate and got errors each time. Now it works, but I got the invalid binary error. It looks like Apple have done some changes and missed up something.
There might be a link between a change in certificates yesterday and the invalid binary error today, which gives a possible explanation of this problem.
I've had the same issue and have found out that my Provisioning Profile for Distribution "somehow" disappeared from the Apple Developer Portal. But when I tried to re-create it, I received error message about the existing one (which I couldn't find at all).
Finally, I've just created a brand new Distribution Provisioning Profile, downloaded and installed it. In the end, I was able to validate the application package and upload was successful.
Just spent a while on this also, my upload previously worked and managed to get through validation.
However, once up Apple would fail/reject the uploaded binary due to something similar to the below
https://stackoverflow.com/questions/18952213/invalid-directory-name-your-app-contains-a-directory-name-that-is-already-rese#=
Upon retrying, later without making any modifications, rather then sucedding then failing after validation I started receiving an error exactly the same as the OP.
Fixing the framework reference issue, enabled me to succesfully upload.
So rather then uploading passing validation and then being rejected, it would not pass validation, and I give the same error, without any hints.
Hopefully this helps someone else.
In my case I updated my Mac version and it worked fine afterwards.
Since upgrading to iOS 6 I have been unable to install the "TestFlight Access" profile, and my clients running 6.0 are experiencing the same issues. I have googled the issue but I am not finding any results.
The error message is just after you enter your device password and reads:
"Profile Installation Failed
A network error has occurred"
I have verified I have a good network connection, and the error is happening at multiple physical locations (different service providers and internet access)
Thanks in advance!
I just had the same problem with our build and one of our testers found this solution:
" advise people to go to settings > general > profiles and remove their profile and then clear cookies / cache, reboot the phone and it should work"
Make sure to remove the TestFlight WebClip profile as well.
Hope this helps!
Ryan