Question 1

How do I set up CloudCore for offline sync in my iOS app?

Accepted Answer

Enable NSPersistentHistoryTracking in your Core Data stack, add required service attributes like privateRecordData and recordName to entities, and call CloudCore.enable in AppDelegate. Changes are queued via NSPersistentHistory when offline and pushed automatically when online.

Question 2

CloudCore vs NSPersistentCloudKitContainer: which is better for my project?

Accepted Answer

Choose CloudCore if you need field-level sync, selective synchronization, or cacheable assets for large files. Opt for NSPersistentCloudKitContainer for simpler, drop-in sync with less configuration, as it handles entire records and has native Apple support but less control.

Question 3

How to handle large files like videos with CloudCore without slowing down sync?

Accepted Answer

Use cacheable assets by conforming to the CloudCoreCacheable protocol, mask asset attributes during sync, and leverage long-lived operations. This separates large file uploads/downloads from regular sync, allowing on-demand access and avoiding timeouts.

Question 4

Does CloudCore support CloudKit sharing with a custom user interface?

Accepted Answer

Yes, it has built-in support for CloudKit Sharing and provides CloudCoreSharingController to integrate with UICloudSharingController. However, it requires additional setup in info.plist and implementing delegate methods for accepting shares.

Question 5

What are the required Core Data attributes for CloudCore to work?

Accepted Answer

For each synced entity, you must add privateRecordData and publicRecordData (Binary type), recordName and ownerName (String type), and enable 'Preserve After Deletion' for the record data attributes. These store CloudKit metadata and ensure proper sync.

Question 6

How to troubleshoot when CloudCore sync fails or data doesn't appear?

Accepted Answer

Check for CloudKit errors like userDeletedZone or changeTokenExpired, verify attribute mappings in UserInfo, ensure NSPersistentHistoryTracking is enabled, and run the provided CloudKit tests in a configured environment to diagnose issues.

Question 7

Can I sync only specific attributes and leave others local with CloudCore?

Accepted Answer

Yes, using maskable attributes, you can designate which attributes are ignored during upload or download by setting CloudCoreMasks in the UserInfo with values like 'upload' or 'download' for fine-grained control.

CloudCore

What is CloudCore?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions