fix: Broken local backups, feature: Google Drive backup groundwork - #67
Merged
Conversation
…t backup profile restore failure
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Profile data was not being restored properly in local backup due to multiple models selfishly calling the same dose.db together causing it to fail to read.
This has been fixed with a centralized model which will handle the database requests.
Fixing this logical error in turn fixes the failing restore function.
Basic framework for the Google Drive backup function has been implemented.
The feature will attempt to sign in to the user's account but will fail as the app has to be verified by Google.
Either you will see an error as a snackbar or a fullscreen popup saying that "Access is blocked" with the same reason as above.