Skip to content
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

Fix async open interaction with read-only Realms #4910

Merged
merged 4 commits into from
Apr 27, 2017
Merged

Conversation

austinzheng
Copy link
Contributor

Changes:

  • async open no longer opens a synced Realm conventionally at the beginning, causing data to be written to the server

This change is verified through a unit test in an upcoming PR. (It is not included in this PR because it contains a large number of upcoming dependencies that would be impractical to port into this PR.)

Changes:
- async open no longer opens a synced Realm conventionally at the beginning, causing data to be written to the server
@austinzheng austinzheng self-assigned this Apr 27, 2017
@austinzheng austinzheng requested a review from jpsim April 27, 2017 22:16
return;
}
}
if (error) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this check just needs to happen in the hasSyncConfig case.

Copy link
Contributor

@jpsim jpsim left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 just needs a bugfix entry in the changelog noting that read-only synced Realms can now be opened using asyncOpen. Resolves #4296.

@austinzheng austinzheng merged commit 5427565 into master Apr 27, 2017
@austinzheng austinzheng deleted the az/fix-async-open branch April 27, 2017 23:06
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 15, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants