Implemented Procedure Push Updates using Firebase Cloud Messaging #2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ID as protocol identifier and version as version
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implemented receiving procedure pushes from Sana Protocol Builder.
The Protocol Builder sends a push notification to the Android app containing a URL to fetch the full procedure XML file from. The Android app then makes an HTTP request to the URL to get the procedure, and saves it locally.
When pushes of different versions of the same procedure are made, only one version (the last version that is pushed) is kept on the phone's database.
Note: bumped up
minSdkVersionfrom 11 to 14 in order to support Firebase Cloud Messaging. This is still compatible with 99.7% of all Android users as of March 2018 (source: https://developer.android.com/about/dashboards/index.html).