(Fix) metadata crash on startup with Local Notification plugin. #1621
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
shiv19
approved these changes
Jun 21, 2020
|
test |
shiv19
approved these changes
Jun 21, 2020
shiv19
approved these changes
Jun 22, 2020
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.
Description
Android 9 & 10 on some phones now enforce the requirement that after a reboot the data is un-accessible until phone has been unlocked once after startup. According to the docs; this was a new feature in Android 7; but we are only seeing crashes in Android 9 and later.
The new error code detects this specific condition and now just exits the application w/o throwing an error, as throwing an error shows up as a error in the Google application error log. After much testing, exiting the app is the safest course of action with no issues because application doesn't actually need to run at this point.
Does your commit message include the wording below to reference a specific issue in this repo?
Fixes #1546
Does your pull request have [unit tests]
No, unable to test except manually (see #1546 for instructions)