Adopt existing share

[davidrothera]

I'm migrating an existing app which uses CoreData and already uses sharing.

Whilst I can handle migrating the data in the private store ideally I need to be able to "adopt" the existing shares between users and add the new records from this library to said share.

Adding additional records to an existing CKShare is easy enough however what I want to be able to do ideally is to use a pre-existing CKShare rather than having the library generate a new one.

[mbrandonw]

Hi @davidrothera, this is a tough one. I'm not sure it can be done as the library is built today, and I believe the root of the problem isn't so much that you have your own shares created in iCloud. I think the bigger problem is that you have your own CKRecords saved in iCloud and SQLiteData isn't going to magically understand those records. The library uses a specific format for its recordNames ("\(primaryKey):\(tableName)"), and it's important for that format to be preserved because it's how we map iCloud records to rows in your database.

So it would seem to me that in order for you to migrate an existing Core Data + iCloud app we would need to allow for mapping your existing CKRecord record names to a primary key + table name combo that the library can use. If that could be done then I think existing CKShares would work automatically because there's nothing about their record names that are important to us. All we need is the hierarchicalRootRecordID from a share's metadata.

How are your CKRecords named currently?