Using Android Autobackup causes wrong runtime permission status

[dpa99c]

I'm submitting a ... (check one with "x"):

• [x ] bug report

Bug report

Plugin versions affected: v4.0.6 and below

Current behavior:

Currently on Android, the plugin stores a flag in HTML5 local storage when a runtime permission is first requested. This is so the plugin can differentiate between NOT_REQUESTED vs PERMANENTLY_DENIED status since natively, the Android runtime permissions API does not distinguish between these states.

However, if you use Android Autobackup in your app, HTML5 local storage will automatically be restored on new app installs, causing the plugin to mistakenly determine a permission has been PERMANENTLY_DENIED when in fact its true status is NOT_REQUESTED.

Expected behavior:

When using Android Autobackup, permission statuses of PERMANENTLY_DENIED vs NOT_REQUESTED should be correctly determined.

Resolution

The solution would seem to be to store the permission request flags using a storage which is not automatically restored when using AutoBackup and can therefore be relied upon to be reset up each new app install.