-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compact doesn't work with synced realms #2345
Labels
Comments
It turns out to be a more complicated problem. Compact doesn't write out the history part of the Realm file. Apparently this confuses the later attempt to reopen the file as a synchronized realm. |
shouldCompactOnLaunch seems to work as a config option on my synced Realm on Realm Cloud. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When I open a synchronized Realm and call
compact
on it, I get a bad history type exception. After brief debugging with the help of @fealebenpae, we concluded thatdo_open
is called at the end ofcompact
, then in theif (Replication* repl = m_group.get_replication())
,m_group
is empty, sorepl
is alwaysnullptr
and thehistory_type
is never set to the correct value.The text was updated successfully, but these errors were encountered: