@DTS Engineer Quinn, Hahah, that wasn't me, I wanted to post on swift.org but didn't, looks like others also spotted the same issue. I can understand must such a rush with so much to do before WWDC A big thanks from my end to the entire team who have done an amazing job!

Xcode 27, Device Hub seems to be working for me on macOS 26.5.1 (25F80). May be you could post a screen recording / screenshot of the error so that Apple Engineers / others can suggest solutions

Thank you so much @DTS Engineer Quinn!! Thanks for the effort of pointing other typos and providing a working code, much appreciated!! Little things trip me up, it would be nice for the presenters show code that actually compiles even if it is only featured for a few seconds. Best to have a demo project to showcase these things.

Problem The actual issue for me is Xcode when adding a new package and entering the URL in the search box where it keeps spinning (even over an hour) never ends. This seems like an Xcode bug Workaround Add one of the Apple Swift Packages which comes pre-loaded with Xcode like swift-algorithms Once added that screen gets dismissed and the swift-algorithms URL is added as a dependency Now click on the swift-algorithms and change it to your URL and also update the Dependency Rule This will add the your swift package and pull the code. DTS Engineer: @DTS Engineer this seems like an Xcode bug.

Once the spinner begins, turning off the WiFi the spinner doesn't stop. Is it really searching? I am surprised no one else is facing this issue.

@DTS Engineer Thanks a lot Ziqiao Chen, Yeah I have used transformable which seems to have resolved the problem. Hopefully this gets fixed because for every custom type (even if it can be represented with a simple struct) this transformation needs to be done which does add a bit of overhead and not as nice / elegant / easy as just using Codable. Thanks again for your help. If you have time there is one other issue regarding CloudKit FB22670054 (https://developer.apple.com/forums/thread/824836)

@DTS Engineer They had asked me to close the bug as it was a duplicate of FB22670054. So I have closed FB22670187

@DTS Engineer Please refer to feedback FB22670054 instead, thanks!

@DTS Engineer I am sorry this is an CloudKit project with entitlements, I don't want to post it in a public forum. You can download it from the Feedback FB22670187. Considerable effort has gone in creating a sample project, so I hope this is being investigated. Regarding the bug, I genuinely think it is a bug, if the team thinks otherwise, please reply to the feedback.

Thanks @DTS Engineer I have created a feedback FB22670187 It contains a sample project and also attached a video Run it on a real device The video shows the log being generated on Xcode. Look at the subsystem of the log, it is from com.apple.cloudkit It contains details about the fault and how to reproduce it.

Sorry if this is something that you are already aware of. Take it with a pinch of salt as my knowledge on this is a bit rusty. Could you check the following? CKQueryOperation.resultsLimit is responsible for the number of record returned. It might be 100, which could be why you get in batches of 100. You can change this value. Is [[CKQueryOperation alloc] initWithCursor:theCursor] is actually getting hit for refetching remaining records ? CKQueryOperation.configuration for qualityOfService. The default qualityOfService might be utility which may not be what you desire. You might need to set it higher qos depending on your needs. If [[CKQueryOperation alloc] initWithCursor:theCursor] is actually hit but the last one didn't complete then it could be the qualityOfService. Try setting it to userInitiated. Just curious It is interesting you are using a public database, is this user data stored in public database or common content? If it is private user data, then would be better to use private database. Even the quota for public database would be counted against your app.

@DTS Engineer Albert, If it is not a lot of trouble would it be possible to check with the SwiftData / CoreData / CloudKit regarding the following: What is the background task ID for the background task? (so that the app can allow it and not block it) It would be greatly helpful to know this because this is done by the framework and by blocking it we might lose some functionality that Apple had intended to provide. Thanks!

Thanks for your responses.

@DTS Engineer, That feedback is for a different issue. Should I create a separate feedback for this task id issue? I was suggesting that project for you to download and test on real device to reproduce the error. If you think you want me to create a separate feedback let me know. I already have a TSI opened and waiting for their response on it. Just got only an automated message. Is there a timeframe for someone to respond to TSI?

@DTS Engineer Albert, thanks for the response. Error Please see the screenshot of the fault log, Subsystem for the log iscom.apple.cloudkit Category for the log is Scheduler Answer to your questions: Cloud sync works and data gets synced, no issue with the data. Yes correct primary sync doesn't happen via BGTaskScheduler. However SwiftData / CloudKit initiates a background task to do some processing. The background is the one that gets blocked. This is a clean new project (no 3rd party libraries) and I have written the code so I am sure of that there is no background task I am initiating. Testing / Sample project: If you really want to test it, please refer to the project attached in FB22634797 Though FB22634797 is for a different issue, the Xcode project would throw the fault log in Xcode. It is a very simple project. Question It would be great if someone from SwiftData / CoreData / CloudKit team can confirm this.