I added a new Core Data model version, introducing a new entity.
Based on the naming of the Entity I get different behaviour:
A: If the entity is alphabetically ordered as last entity: Everything works fine.
B: There entity is ordered before already existing entities:
My only workaround so far is to just give the entity a different name, to appear last in the list.
__
Does anyone else experience this issues? I am not sure if my code could be able to trigger this kind of behaviour.
I will try to reproduce it in an empty project, to file a bug report.
Based on the naming of the Entity I get different behaviour:
A: If the entity is alphabetically ordered as last entity: Everything works fine.
B: There entity is ordered before already existing entities:
All records of these existing entities get a new CloudKit id. Resulting in duplicated data and broken relations.
In some cases the seem-to-be new insert of these records causes the migration to fail. (Constraint unique violation, reason=constraint violation during attempted migration)
My only workaround so far is to just give the entity a different name, to appear last in the list.
__
Does anyone else experience this issues? I am not sure if my code could be able to trigger this kind of behaviour.
I will try to reproduce it in an empty project, to file a bug report.
