has duplicate

[victorcode1]

....

[sync-by-unito]

➤ PM Bot commented:

Jira ticket: RDART-995

[nielsenko]

Did you make Entity.id a primary key, when updating the schema?

[nielsenko]

Realm is complaining that there are multiple objects with the same id after the migration, which is now illegal since it has become a primary key.

You need to remove all duplicates. The simplest thing is probably to just delete the realm entirely, if you can afford to loose the content.

[nielsenko]

Yes, it would affect any user who updates. You should only delete the realm, if you can afford to loose the data in it.

If you have customer data you need to preserve, then you need to either drop making id unique, or remove duplicates explicitly in your migration callback to avoid the issue.

Is it by any chance so that all id values are null? If you added the id column as part of the schema change, then it needs to be populated for all existing entries as part of the migration.

[nielsenko]

Read up on: https://www.mongodb.com/docs/realm/sdk/flutter/realm-database/model-data/update-realm-object-schema/#other-migration-tasks.

If you sort Entity from oldRealm on _id you can find the duplicates.

[nielsenko]

Migration is currently only for local realms. See https://www.mongodb.com/docs/realm/sdk/flutter/realm-database/model-data/update-realm-object-schema/#updating-the-schema-of-a-synced-realm

Embedded objects are used for aggregate types. One advantage is that you don't have to setup dedicated subscriptions for embedded objects. They always follow their parent.

[nirinchev]

Can you post the error message with the full stack trace?