Skip to content
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.

Sign up for GitHub

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

Jump to bottom

More reliable way to determine new autofill save requests #9

Open
luckyrat opened this issue May 4, 2022 · 0 comments
Open

More reliable way to determine new autofill save requests #9

luckyrat opened this issue May 4, 2022 · 0 comments
Assignees
@luckyrat
Labels
question Further information is requested

Comments

@luckyrat
Copy link
Member

luckyrat commented May 4, 2022

Maybe a parcelable unique ID?

Current implementation relies on consistent JSON stringification of Android-supplied metadata so not sure if one of these issues can occasionally occur:

  • App fails to return to normal mode after restore following aborted autofill save attempt
  • App fails to save supplied credentials if they are the same and from the same source as the most recent request to save
@luckyrat luckyrat added the question Further information is requested label May 4, 2022
@luckyrat luckyrat self-assigned this Aug 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@luckyrat luckyrat

Labels
question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@luckyrat