-
Notifications
You must be signed in to change notification settings - Fork 31
STITCH-2263 - Android SDK: Always run R2L synchronization first #84
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM mod two nits
README.md
Outdated
1. In Android Studio, go to Tools, Android, AVD manager. | ||
2. Click Create Virtual Device. | ||
3. Select a device that should run your app (the default is fine). | ||
3. Select a device that should run your app. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[nit] maybe add a note that the "default is not fine", since as of Android Studio 3.2 the default is x86, which does not work.
4. Select and download a recommended system image of your choice (the latest is fine). | ||
* x86_64 images are available in the x86 tab. | ||
* This device must a system image built on an architecture supported by the | ||
```libmongo``` library, e.g. x86_64 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[nit] maybe point to https://docs.mongodb.com/stitch/mongodb/mobile/getting-started/
Per our decision, this commit removes the ability to (in code) swap from R2L first to L2R first behavior and eliminates the resulting duplicate test sequences. This change complies with our updated specification and ameliorates the need to make sure that all behaviors work across both directional preferences. Neither preference offered significant advantage to end users and complicated the logic when versions were missing during synchronization, as versions are not persisted locally.