Version mismatch does not block sync about realm-js

[sync-by-unito]

➤ PM Bot commented:

Jira ticket: RJS-2795

[HugoBounoua]

@kneth Is there a way to specify a version number to Realm and not allow Realm to sync if there is a version mismatch? A solution to not impact and destroy all data until the app is updated?

[kneth]

@HugoBounoua I am curious to know if you use RecoverUnsyncedChanges as client reset mode?

v12.6.0 has a upgrade to Realm Core with realm/realm-core#7239. Do you use flexible sync?

[nirinchev]

I'm curious about

Create migrations to adapt local data to the new schema and publish them on the app store

Unless RealmProvider does something I'm not aware of, onMigration should only apply to local Realms and should never get executed for synchronized Realms.

Additionally, server-side schema migrations is not a feature that is enabled by default across all apps yet. Have you requested that it manually gets enabled for your app?

[danieltabacaru]

Have you requested that it manually gets enabled for your app?

I don't think that's possible yet. Also, this will be done automatically soon by the client if async open is used (so users need connectivity) and the new schema contains the following subset of breaking changes (remove table, remove property, change optional property to required, change required property to optional)