Hi Tyler, thanks for the details.
I didn’t know about the default value, I just used it for another schema change (added a required property) and I had no issues.
This is actually a good way to have the app work with old mobile clients who can create unsyncable data, without having to set up triggers and do migrations for simple changes. It’s weird that I don’t remember seeing it in the docs.
I forgot to mention one thing - I also tried doing a realm refresh and syncSession resume/reconnect right after opening the realm (with downloadBeforeOpen set to .once) but it still didn’t sync, even though I had added the required property in the database.
Could it be that the objects were not marked back as syncable after I added the data to comply with the schema?
(unrelated - I can’t deploy my production app, can you take a look please?)