Correct docs about what is ignored in full-data backup
You can't back up content in e.g. getNoBackupFilesDir() even if your app explicitly tries to. Bug 28321431 Change-Id: Ifa2a4bc518de03aba4c8809e60d8bb90fce767f8
This commit is contained in:
committed by
Chris Tate
parent
47384f90b4
commit
c5be8f8a4b
@@ -488,9 +488,11 @@ public abstract class BackupAgent extends ContextWrapper {
|
|||||||
* to place it with the proper location and permissions on the device where the
|
* to place it with the proper location and permissions on the device where the
|
||||||
* data is restored.
|
* data is restored.
|
||||||
*
|
*
|
||||||
* <p class="note">It is safe to explicitly back up files underneath your application's
|
* <p class="note">Attempting to back up files in directories that are ignored by
|
||||||
* {@link #getNoBackupFilesDir()} directory, and they will be restored to that
|
* the backup system will have no effect. For example, if the app calls this method
|
||||||
* location correctly.
|
* with a file inside the {@link #getNoBackupFilesDir()} directory, it will be ignored.
|
||||||
|
* See {@link #onFullBackup(FullBackupDataOutput) for details on what directories
|
||||||
|
* are excluded from backups.
|
||||||
*
|
*
|
||||||
* @param file The file to be backed up. The file must exist and be readable by
|
* @param file The file to be backed up. The file must exist and be readable by
|
||||||
* the caller.
|
* the caller.
|
||||||
|
|||||||
Reference in New Issue
Block a user