CloudKit Dashboard - Cannot add or update asset items

I've been using CK Dashboard for several years to maintain updates that propagate to user apps. Recently I have had a problem adding or updating any record that has an asset in it. Adding the asset seems to go fine until I hit the "Save" button. Then it comes back with "! Load Failed". This happens every time. I'm using the latest build of Safari in Big Sur 11.6.1. I have searched preferences to see if somehow Safari does not have access permissions, but it does not matter what directory the uploaded file resides in - it fails every time. I can download a record with an asset, but if I change the asset and save, it fails. Saving from a live app in iOS continues to work fine. This seems to be some sort of permission issue, but I am the only user and I have all permissions enabled. Logging out/back in has no effect. This problem exists in both my M1 iMac and M1 MacBook Air (Monterey). Looking for anyone else having the problem before filing a bug.

Replies

It seems your browser is blocking the request to upload the asset. To unblock your workflow, you might want to try another bowser. To help us track down the cause, could you please send us anything you see in the browser Console (error message, stack trace) after the request has been failed.

Add a Comment

Very strange workaround passed along to me from elsewhere:

Downloading Opera and enabling the free Opera VPN resolved the issue uploading assets for me. Likely something to do with DNS or my IP provider. 🤷

Thanks for the suggestion. It did not solve the problem. I suspect that you're right about DNS or ISP, and I have a hunch my Eero router might be involved.

Im having the SAME issue. This used to work before apple "updated" Cloudkit dashboard smh. I'm almost ready to exclusively use a different database altogether. I HATE Cloudkit dashbaord.

  • I’ve experienced the same issue directly with the CloudKit Asset upload API. Calling the API to get the URL for upload always works. But then that URL itself usually doesn’t resolve in DNS. This all began for me on Nov 1 and the problem has continued ever since. I’ve tried changing the DNS used for resolution and that hasn’t helped. I see the TTL on these domains are 30s so not sure if that’s a recent changed related to the issue or not. We have cron jobs that regularly upload fresh data via this Asset upload API. As a workaround, we’ve added many retries but it often takes 5-10 retries to succeed. Our crons run python scripts which fail with error “Failed to establish a new connection: [Errno 8] nodename nor servname provided, or not known” when attempting to connect to domains such as p48-contentws.icloud.com.

Add a Comment