Explain vault backup permission error #1233
Merged
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
Users understandably get confused by the "No persisted URI permissions" error. This patch adds some text to the dialog explaining why this happened and how the user can fix the issue. This permission issue can happen for one of two reasons: - The user made a change to the backup destination (renamed, moved, deleted, etc) - Aegis was restored from an Android backup
michaelschattgen
approved these changes
Nov 29, 2023
Closed
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.
Users understandably get confused by the "No persisted URI permissions" error. This patch adds some text to the dialog explaining why this happened and how the user can fix the issue.
This permission issue can happen for one of two reasons:
Closes #1230.