diff options
| author | Christopher Tate <ctate@google.com> | 2011-06-03 12:27:51 -0700 |
|---|---|---|
| committer | Christopher Tate <ctate@google.com> | 2011-06-03 14:06:46 -0700 |
| commit | a858cb075d0c87e2965d401656ff2d5bc16406da (patch) | |
| tree | a184d02d871a906a5b3192bcec5f3495a2a97f21 /packages/BackupRestoreConfirmation | |
| parent | 507fc54924af53635e8d5520e5836c046af00775 (diff) | |
| download | frameworks_base-a858cb075d0c87e2965d401656ff2d5bc16406da.zip frameworks_base-a858cb075d0c87e2965d401656ff2d5bc16406da.tar.gz frameworks_base-a858cb075d0c87e2965d401656ff2d5bc16406da.tar.bz2 | |
Respect android:allowBackup="false" during full backup & restore
Packages with this manifest attribute set 'false' will not be backed
up even through the "full device backup" infrastructure. If someone
produces an apparent restore file with data for such an application,
it will not actually be restored onto the device.
When an apk is installed during the course of a restore operation,
it is validated against the manifest contents and deleted if there
is a mismatch. Also, if the newly-installed app is found to
disallow backups, no file content will be processed for that app.
Bug 4532159
Change-Id: I59630054584b1394e567de939192e22e597044ee
Diffstat (limited to 'packages/BackupRestoreConfirmation')
| -rw-r--r-- | packages/BackupRestoreConfirmation/AndroidManifest.xml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/packages/BackupRestoreConfirmation/AndroidManifest.xml b/packages/BackupRestoreConfirmation/AndroidManifest.xml index ed9a519..19848f6 100644 --- a/packages/BackupRestoreConfirmation/AndroidManifest.xml +++ b/packages/BackupRestoreConfirmation/AndroidManifest.xml @@ -21,7 +21,7 @@ <uses-permission android:name="android.permission.BACKUP" /> <application android:allowClearUserData="false" - android:killAfterRestore="false" + android:allowBackup="false" android:permission="android.permission.CONFIRM_FULL_BACKUP" > <activity android:name=".BackupRestoreConfirmation" |