More reliable way to determine new autofill save requests

[luckyrat]

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