-
Notifications
You must be signed in to change notification settings - Fork 1
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
Chore
: Set tum artemis server as default
#257
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!
I addressed your comments and the BottomSheet now opens in full screen. EDIT: I now also added the host url for non-debug build, but only if the user has selected a custom instance. |
… in production for selected CustomInstance
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.
Just tested your changes and I did not notice any issues. The code changes seem appropriate.
Problem Description
The current Artemis Android release in the Play Store uses the "Tum" build flavor, which does not allow instance (artemis server) selection. Simply switching the released build flavor to "unrestricted" would have caused already logged in users with weird behaviour (all network calls would fail because it would try to reach the artemis server via localhost; only a logout and sign in again would have resolved this issue).
Changes
serverUrl
instead of the duplicated logic withhasUserSelectedInstance
hasUserSelectedInstance
Feature
: Add navigation animations #222, as it removed theNestedDestination.InstanceSelection
navigation target, but did not remove it in other places of the code. This would lead to an app crash just after freshly installing the app.Steps for testing
Scenario 1 - Updating the app from "tum" to "unrestricted" flavor
:app
:app
Scenario 2 - Fresh install
:app