Initial properties not available when sync failed

[Ezor]

Hi,

Here is the failing scenario :

• Create an NSManagedObject with the following properties : firstname = 'John', lastname = 'Doe'
• Save context
• CloudCore try to sync this new Object but if fails for whatever reason (iCloud not available, limit exceeded...). So we don't have the corresponding CKRecord in CloudKit.
• Later, we update the same NSManagedObject : firstname = 'Jane', lastname = 'Doe'
• CloudCore create a CKRecord with only updated properties : firstname = 'Jane'

So on CloudKit, we will never have the property set during NSManagedObject creation, here lastname = 'Doe'.

I'm not sure how it could be fixed apart by always updating all properties.

[Sorix]

That's really a big problem, I need to think how to handle it. It can be handled automatically or I need to send "failed" syncs to some delegate, so your application will decided what to do (try to re-sync and discard changes).

I will place it to my to-do list, thank you.

[Ezor]

Well I think iCloud synchronization must not affect the way we add, update or delete data.
My idea is CloudCore should detect that we need to upload all properties again maybe using a property on the ManagedObject (like lastSyncFailed = 1).

On my fork, to fix this temporary, I updated the code to upload all properties each time.

[pocreations]

Hi Julien, Could you tell us please how did you change your fork so that all attributes are saved each time to the cloud (not only those who changed) ? Thanks, Ismail

…

Le 30 mars 2018 à 22:12, Julien Rozé ***@***.***> a écrit : changetype

[Ezor]

Hi,

Ezor@01b680a

[pocreations]

Thanks a lot!

…

Le 10 avr. 2018 à 19:16, Julien Rozé ***@***.***> a écrit : Hi, ***@***.*** <Ezor@01b680a> — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#31 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AX1P3vBHJtUUa5K_Z3Ldbkp0LIQ-w8ZFks5tnOj6gaJpZM4TCFxw>.

[rockylive]

Hi @Ezor

I also had the problem where some properties getting nil (Adding cloudcore to existing db). I tried your fix and it's ok with newly created DB or entries. but if you have existing DB, and enabling cloud core with your fix will crash the app in launch.

This is the place it get stopped