I'm working on an app where I recently decided to go with CloudKit and am now at the point where I need to implement the backend functionality. In a nutshell, this app will use a collectionview to display images retrieved from a CK database. Up until now, I just dumped some images in a folder on my desktop and retrieved/parsed the images from there to render the collectionview. I then used the CK dashboard to create some records and wrote an initialization method to try and retrieve them. I was getting various CKErrors, such as network failure, error completion without receiving a response from the server, could not send a valid signature, etc. I immediately assumed the issue was with my code since it was my first attempt with CloudKit. However, I ran the latest code on my device before posting on SO and it worked! I got a successful response with the number of records in the results array that I was expecting.
So now I know longer need help with fetching CKRecords like I initially thought. But how do I resolve this issue with the simulator? I saw some other post about making sure you're signed into iCloud on the simulator. I believe I am, but do not know how to check to be sure. Also, I'm running Yosemite and Xcode 6.1.
Any help is appreciated!
on the simulator go to the settings app. You can do that with menu hardware, home and then open the settings app, select iCloud and make sure that you are logged in.
To use your Apple ID on iCloud on the iPhone Simulator, make sure you turn off Two-way authentication. It should then work on the simulator.
Related
I have an application for macOS that uses core data to save data. I switched to CloudKit so I can sync that data with its iOS counterpart. This is on Xcode 13.4. Even since I did that I get the error:
When I try to submit it for a distribution with "Developer ID"
I have been going in circles for the last two days. I have tried all the stuff several articles here at SO mentioned (e.g. this one), or the Apple Dev Forums (for example this one). I have tried deleting certs, regenerating them, adding them again, downloading "manual profiles" again, going to the building settings and changing certs and options...
It doesn't matter. It goes nowhere.
Here's the thing, if I go back to the version without iCloud, all is good. Same with any iOS app that uses iCloud. All builds, and all goes to Apple without any issues. It's only this app.
For the sake of testing I created a new macOS app, and from the get go I enabled CloudKit. Same error.
So, what's missing? Is there any special foo or incantation I need to utter to get an macOS app to use iCloud and be able to be distributed?
Thanks
I am just trying to update the old version with the new one. I am using the latest version of Xcode (version 6.4) and I validate my app bundle before submitting the app.I submit it from Xcode to iTunes Connect.
After all the setup, when I clicked on the Submit for Review button I got error like below.
The app's Info.plist can't contain values for the UIRequiredDeviceCapabilities key that would prevent this app from opening on any iOS device.
I check in my project .plist file there is appear like following screenshot.
But I don't know why this error occurred during the submission of the app.
As some of the comments above state, you have two options here.
Option 1:
You delete the key from the plist entirely. Wouldn't recommend that as you want it to run only on devices with armv7
Option 2:
You can add the normal architecture of 64 to the plist. This will allow it to run on more devices, thus also getting it successfully submitted.
Lastly, you could try to use Application Loader. There's a small chance this will actually make a change, but it doesnt cot anything and is worth a try. If nothing works out, you can contact iTunes Connect at: ituesconnect#apple.com
Hope that helps, Julian
I did fixed this issue by I removed the UIRequiredDeviceCapabilities from Project Plist and then create IPA and upload it to iTunesConnect.
Then that will be submit without this error.
Maybe you must check your Build Settings. I have your same .plist and I don't have any trouble to upload to App Store.
Check this values:
I just loaded Xcode 6 GM seed. Now I want to submit an update of my app.
Archiving works so far. But when I click "Submit", as soon as the upload loading bar appears Xcode crashes.
Do I need Yosemite?
I had to download the Application Loader from Apple because Xcode could not find it.
Do I need Yosemite?
No. Mine crashed the same way, so i uploaded my app using Xcode 5.1. It worked fine.
The Application Loader seems the only thing that works right now. Had the same problem, while uploading or even just validating.
Just export via Organizer and Upload via Application Loader helped.
I was faced same problem. Now it works fine.
Solution : Just accept new changed terms and condition from apple developer account and resubmit it.
Please Make sure you've accepted all of the new agreements & condition in the Member Center.
To check if you need to, you can go to the preferences -> accounts in XCode, and chose to view details of an account and attempt to refresh button. Here, XCode will warn you that you need to accept new agreements in the Member Center before you can refresh.
or just login to developer account and go to here https://developer.apple.com/membercenter/index.action
I was able to make Xcode work, but I had to go to iTunes connect and start the process there first by going "My Apps" and clicking on the plus sign. Fill in the info and hit save. Then try submitting with Xcode and it should work.
OK. Here's my $0.02.
1) Xcode 6GM crashes every single time for me. I am running 10.9.4. I have no idea how widespread the issue is, but it is 100% repeatable for me. I cannot use Xcode 6 to submit apps for review.
The crash happens during the upload. I have submitted a RADAR report and given crash logs.
2) I was able to submit using the App Loader. Here's how you do that:
2.1) In the Organizer, after you have done the Archive, select the latest archive for submit.
2.2) Instead of "Submit," select "Export."
2.3) Select the first choice (App Store).
2.4) Open the Application Loader.
2.5) Select "Choose."
2.6) Select the .ipa that you just saved in the export.
2.7) That will work. You may get a message teling you that the API file is too big for analysis. I got that for all 9 of the apps I just submitted. In my case, I ignored it.
I think they rewrote the whole application load from scratch, and that Xcode is still buggy as hell.
They had a deadline, and rushed it. It shows.
I expect both the server (Web) component and Xcode to apply patches soon.
In my case, I'm quite annoyed, as I had to rush out a fix for the arbitrary decision they made to change the way that the CLLocationManager works, which broke all my location lookups. The fix is simple, but there will be a period of time when I receive hate mail from the users that upgrade to iOS 8, and the app stops working.
Joy.
I just installed the official version from the App Store and now everything works fine.
I had the same problem. When XCode crashes during export or submit it means that you have non-valid certificate or provision profile in build settings.
Here is the solution:
Accept new changed terms and condition from apple developer account. (Just like Sandeep said)
Go to here to generate new provision profiles, for App Store & AdHoc (Tutorial)
Double click new provision profiles you downloaded to install them, and then XCode will never crash.
The problem is caused by XCode 6.0 does not handle provision profile migration properly. Developers should regenerate provision profiles for XCode 6+, but Xcode 6.0 fails to display this error message properly and crashes. (If you use XCode 6.1 Beta, it will display error messages for you, no crash. Then you will know that the problem is caused by "invalid"=="legacy" provision profile.)
After that, you can submit app and export Ad Hoc distribution for Testflight.
My app is ready to upload. Everything works fine in development side. I wonder what I should change (about SSL or something else) before uploading to store?
This is a complex topic and we may not be able to answer this in once sentence.
For submission you may need a Distribution Profile from the Apple Dev Center. Depending on the functionality you're using in your app, and depending on if it's an iOS or Mac App, you may be able to use the provisioning profile Xcode has generated for you. You can set this under Build Settings - Code Signing - Provisioning Profile.
You also need to setup your app in iTunes Connect so you can submit it (this includes screenshots, App Store Category, description, etc).
To check if the submission will be successful, head over to Product - Archive, and from the screen that opens hit "Validate". This will tell you if you're missing anything.
Take a look at the App Distribution Guide for details on how to submit an app to the App Store. There's a whole chapter on Push Notifications in there too which deserve special attention: https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/AppDistributionGuide/SubmittingYourApp/SubmittingYourApp.html
Those technicalities aside, make sure that any NSLog and NSAssert statements that you may have used while developing are removed or not compiled before submission.
Been trying tonight to obtain a receipt for my app. However, I've been unsuccessful. Here's the steps I've done:
Code signed with developer cert
Made sure minimum version in the info.plist is 10.7
Checked for the presence of the receipt file and called exit(173) if not found
Built from XCode 4.2
Added a new version of the app and some in-app metadata in itunesconnect. The app status is now waiting for a new binary.
I've then done clean, build, right clicked on the app in XCode's project view and opened it in finder to launch it, hopefully failing validation and pulling a receipt back from the store.
However, this never seems to happen (don't get asked for any itunes login etc) and the app terminates immediately.
I've also gone through an entire build/archive/create installer type process as well but that didn't pop up the login either.
Am I missing something obvious?
Thanks!
I've finally got it working. In case anyone else has a similar problem, the real help for me was finding out about console.app. In running this I could see my app didn't appear to be signed.
I deleted all the certificates etc and re-installed new ones. Seems it HAS to be the Mac 3rd party developer. Nothing else seemed to work.