-
Notifications
You must be signed in to change notification settings - Fork 40
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
Users wants to open a local Realm file with server-side sync history #870
Comments
Since this came up in the context of customer (was confused and thought that server realm was broken) I put this higher up in prioritization. |
Studio needs an a change in Realm JS for this to happen. |
Hey Guys, I'm trying to convert from a self-hosted Realm Server to Realm Cloud but want to migrate our data and ran into this. What's the workaround with this so we can at the very least see our data in the Thanks! |
@joshuapinter : we should be able to help with this. Would you mind opening a ticket in our support forum, e.g. https://support.realm.io/ ? Please provide available details for your cloud account as available. |
Thanks, @roberhofer. I created Support Ticket #2499 Unreachable User Data on Realm Object Server 2.4.2. here: |
➤ Brian Munkholm commented: We wont focus on server side use cases for Studio given the migration to MongoDB Realm. |
Describe the bug
A user cannot open a local Realm file copied from a Realm Object Servers
data/sync/user_data
directory. There used to be only Realms without history and Realms with client-side history. Now there is also a type of Realms with server-side history, which is why we havn't seen this before.To Reproduce
Steps to reproduce the behavior:
data/sync/user_data
directory as a local file.Expected behavior
It is expected that any local Realm-file can be opened with Realm Studio.
Screenshots
See #392 (comment)
Versions:
Additional context
This issue could easily be confused with opening a Realm file that has client-side history: #392
The text was updated successfully, but these errors were encountered: