You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have read the FAQ and it doesn't cover my request.
I have searched the issue tracker for open and closed issues that are similar to the feature request I want to file, without success.
I'm on the latest version.
I'm not using a test build (alpha/beta/release-candidate).
This issue contains only one feature request.
Problem Description
Some apps have allowBackup set to false. These apps have a much higher chance of a restore failing.
Sometimes but not always there are good reasons for a developer specifying this, because backups will not work properly. For example, the app may store data that is encrypted by the hardware/TPM, so migrating to another device will fail to decrypt. Restoring may also cause crashes. I have encountered this personally in multiple apps.
Although Neo Backup can and should continue to allow backing up these apps and their data, the user should be made aware that the backup may fail to restore correctly so the user can take precautions, such as performing a backup from within the app or manually exporting app data via other means.
Proposed Solution
Indicate if an app has allowBackup set to false on the apps list and the app page. Also allow filtering by allowBackup=true and allowBackup=false. Maybe also a warning (that can be disabled in settings) when backing up and restoring apps that do not allow backup.
Alternatives Considered
There is no clear and easy way to obtain this information from within Android. The only way to ensure a restore will work is to test each restore individually and manually inspect each app that all important data is still there, which is infeasible for a large list of apps, and unnecessary for the majority of apps. It is much more feasible to do this only for the smaller list of apps that have allowBackup set to false which have a higher chance of failure.
Relevant information
N/A
The text was updated successfully, but these errors were encountered:
Guidelines
Problem Description
Some apps have
allowBackup
set tofalse
. These apps have a much higher chance of a restore failing.Sometimes but not always there are good reasons for a developer specifying this, because backups will not work properly. For example, the app may store data that is encrypted by the hardware/TPM, so migrating to another device will fail to decrypt. Restoring may also cause crashes. I have encountered this personally in multiple apps.
Although Neo Backup can and should continue to allow backing up these apps and their data, the user should be made aware that the backup may fail to restore correctly so the user can take precautions, such as performing a backup from within the app or manually exporting app data via other means.
Proposed Solution
Indicate if an app has
allowBackup
set tofalse
on the apps list and the app page. Also allow filtering byallowBackup=true
andallowBackup=false
. Maybe also a warning (that can be disabled in settings) when backing up and restoring apps that do not allow backup.Alternatives Considered
There is no clear and easy way to obtain this information from within Android. The only way to ensure a restore will work is to test each restore individually and manually inspect each app that all important data is still there, which is infeasible for a large list of apps, and unnecessary for the majority of apps. It is much more feasible to do this only for the smaller list of apps that have
allowBackup
set tofalse
which have a higher chance of failure.Relevant information
N/A
The text was updated successfully, but these errors were encountered: