It's really really sad that this problem has a high search ranking on Google, and yet remains unanswered by Apple or anyone else.Also having this error, and ZERO luck finding the answer. This problem listed here is 4 years old.. crickets. Come'on Apple, ***?

Yes, and no one can find the answer bc Apple forums ROT.

What does this mean Spok?Schema? Security Rules? What? Where are these things?

On your simulator or you iPhone, go to setting and sign-in to iCloud. Users are not allowed to WRITE (CREATE) records to CloudKit unless they are signed-in to Apple iCloud. This is what causes this Permission Error. Apple should obviously add more color to their error; it shouldn't be so hard for devs to debug it (but it is).

In either you simulator or your iDevice, go to settings and sign-in to Apple's iCloud. Users are not allowed to write (CREATE) to CloudKit databases unless signed-in. Signing-in, via Settings, will get rid of 10/2007 "Permission Failure" "CREATE...." error.

ok, but you didn't explain the procedure you used to "add the index". So this isn't helpful. Nowhere in the CloudKit dashboard (circa Fall 2019) is there a navigable area to "make the recordName queryable". ???

A "Permission Failure" error typically means you didn't sign-in to Apple iCloud on the device you are using to run your app. That includes running on iDevice Simulator. The fix is to go to the device's "Settings" and log-in to iCloud. Once this is done, you shoud be able to run your app on that device without getting Permission Failure. Not sure what happens if you use the new Apple Authentication code (circa Fall 2019). Perhaps that would also eliminate the problem from occuring. iCloud doesn't let a User write to CloudKit unless they have an Apple ID and are logged-in to that ID. Typicallly your phone will be logged-in, but when using Simulator prolly not!

Does anyone at Apple actually read these forums and help anyone?NEVER do I find a helpful answer on forums.dev so always have to either go to Stack Overflow or wait on a long phone call for help directdly from apple, probably wasting everyone's time.Can't login to simulator even using the exact same login as used to login here to forums. REALLY annoying. Even built a whole new AppleID and that didn't work either.So can't use simulator to develop anymore. ABSURD problem.

In 2020 this problem probably has to do with all the jiggering of Provisioning Profiles (whatever they are) Apple has recently done but didn't inform anyone.1) Go to developer account, sign in, and sign the new thing they want signed2). then follow this....To fix this, you need to transfer the Provisioning Profile's Certificate to YOUR own certificate. In developer.apple.com, login to your developer account. Then, in the Edit iOS Provisioning Profiles page in Certificates section, select the certificate you are using for your XCode. Then click Generate button.then you'll still have problems, but will be farther along.

Select the UICollectionView in the View Controller Scene menu (middle of Xcode, but left of Main Storyboard visual), and then in Size Inspector change the "Estimated Size" from AUTOMATIC to "NONE". If you have all your hookups done correctly, and constraints are correct in your main Storyboard scene, you should see approximately what you designed instead of small cells.

It's been a year now, and Apple needs to address these M1 related errors. It's messy coding, and we also shouldn't have to do an extra enabling of Rosetta to get things to work in the first place.

I get this problem as soon as my app starts, no API call is even made. Depressing, as nothing is worse than consoleLog filling up with stuff and developer having zero clue if its leading to OTHER problems in the app.

Nice of Apple to respond to this one. These forums are truly as awful as Apple's Swift documentation.

It's incredibly disappointing Apple allows this type of error to persist almost 2 years after the launch of the M1 chip. It's a total disgrace for the company, as they obviously no longer care about bringing on new developers. Apple continues to persist problems with all XCode when it comes to running on M1/M2 machines. And they are totally asleep at the wheel when it comes to these forums. EXTREMELY disappointed in Apple.

You shouldn't have to switch Rosetta on and off just to run a Playground to teach a kid how to code in Swift/XCode/Apple-environment! Most devs don't even understand what Rosetta is, but are forced to figure it out just to continue developing on M1/M2 machines. This is the type of stuff which will lead to Apple's demise.