0

When I open my synced realm, it closes with this message:

Bad changeset received: Assertion failed: left().link_target_table_ndx == right().link_target_table_ndx

This post says that this happens when you're trying to sync two incompatible schemas. However, I've deleted all the local and synced Realms that deal with this data, and then re-created and repopulated the local and synced realms, all using one app, so they have the same schema, don't they? I had previously used a separate app to populate the online realm, and the schema was different and I was getting problems, but I haven't used that app in weeks, and have deleted and re-created the realms since then, so I would imagine this other app shouldn't matter, right?

What's wrong here?


Now, I do seem to be able to avert this Bad changeset message, and the closing of the realm, by including "/~/" in my realm address, which, if I understand correctly, gets replaced by some device-specific ID. I see this ID tacked on in the realm address when I log onto my server in the realm browser, it makes sense to me. But I would imagine you'd want to leave this out and NOT have a unique ID, otherwise every user is creating their own realm on my server and not even actually syncing with anything at all!

It does occur to me that the address without the "/~/" (the problematic one) might be the address I used for the old app I mentioned earlier. But, as I said up there, the realms have been reset so that doesn't make sense. (assuming that deleting realms from the server and then regenerating them from the app is the same thing as resetting!)

This issue is also related to my post here.

Community
  • 1
  • 1
Jonathan Tuzman
  • 11,568
  • 18
  • 69
  • 129
  • Bad changeset means the version of client Realm is forwarded than Server Realm. You said you deleted the Realm file. Is it the cause of the issue? Do you reproduce it again on even after setting up a new server? – kishikawa katsumi Apr 26 '17 at 16:18
  • Usually accessing a realm that doesn't exist creates that realm. Or do you mean reproduce the error? I don't plan on setting up a new server, that seems unnecessary, no? – Jonathan Tuzman Apr 27 '17 at 18:30
  • Standalone Realm works so. But you're using synced Realm. It looks like you replaced the Realm synchronized manually, is it correct? If so, it will not work. – kishikawa katsumi Apr 28 '17 at 16:30

0 Answers0