首页 文章

安装后1分钟应用程序数据清除 - BackupManagerService Timeout

提问于
浏览
3

我刚刚将我的应用程序更新为API 23.每次我更喜欢全新安装时,我都可以使用该应用程序大约一分钟才能崩溃,到目前为止我输入的任何数据都会消失 . 以下是事实:

  • 我一直在使用相同的Google帐户在物理设备和模拟器上进行测试,包括调试版本和已签名的APK . (日志中"Signature mismatch"的可能原因 . )

  • 尝试还原时,日志显示"Signature Mismatch"消息 .

  • 60秒后,日志显示 E/BackupManagerService: Timeout restoring application ...

  • 该应用程序然后被强制杀死,我看到很多关于 clear dataClearDataReceiver 以及 AccountUtils: Clearing selected account for [package] 的条目

为什么会这样?是否由于签名不匹配?为什么操作系统会因为还原失败而清除用户数据?

我的清单中的备份配置:

<application
    android:name=".MyApplication"
    android:allowBackup="true"
    android:backupAgent="MyBackupAgent"
    android:fullBackupContent="@xml/mybackupscheme"

备份方案(默认)

<?xml version="1.0" encoding="utf-8"?>
<full-backup-content>
</full-backup-content>

我的备份助手:

public class MyBackupAgent extends BackupAgentHelper {

    @Override
    public void onCreate(){
        Log.d("MyApp.MyBakAgent", "onCreate called");

        FileBackupHelper myDb = new FileBackupHelper(this, "../databases/" + DBAdapter.DATABASE_NAME);
        addHelper(DBAdapter.DATABASE_NAME, myDb); 
    }

    @Override
    public void onBackup(ParcelFileDescriptor oldState, BackupDataOutput data,
         ParcelFileDescriptor newState) throws IOException {
        Log.d("MyApp.MyBacAgent", "onBackup called");
            synchronized (DBAdapter.dbBackupLockObject) {
                    super.onBackup(oldState, data, newState);
            }
    }

    @Override
    public void onRestore(BackupDataInput data, int appVersionCode,
                    ParcelFileDescriptor newState) throws IOException {
            Log.d("MyApp.MyBakAgent", "onRestore called with version " + String.valueOf(appVersionCode));
            synchronized (DBAdapter.dbBackupLockObject) {
                   try {
                       super.onRestore(data, appVersionCode, newState);
                   } catch (Exception ex){
                       ex.printStackTrace();
                   }
            }
    }
}

相关的LogCat(过滤提及包,可以提供更多)

01-11 21:37:10.881 3588-3588/? D/RCPManagerService: App Installed with packageNAme = com.NSouth.NSouthApp
01-11 21:37:11.311 3588-3588/? D/BackupManagerService: Received broadcast Intent { act=android.intent.action.PACKAGE_ADDED dat=package:com.NSouth.NSouthApp flg=0x4000010 (has extras) }
01-11 21:37:11.311 3588-3588/? D/BackupManagerService: Now staging backup of com.NSouth.NSouthApp
01-11 21:37:11.331 3588-3588/? V/EnterpriseBillingPolicyStorage: getBillingProfileForVpnEngine - start - com.NSouth.NSouthApp
01-11 21:37:11.391 3588-3588/? D/KnoxMUMContainerPolicy: packageInstalledForExternalStorage com.NSouth.NSouthApp

. . .

01-11 21:38:10.241 3588-4061/? E/BackupManagerService: Timeout restoring application com.NSouth.NSouthApp
01-11 21:38:10.251 3588-4061/? V/ApplicationPolicy: isApplicationStateBlocked userId 0 pkgname com.NSouth.NSouthApp
01-11 21:38:10.251 3588-4061/? I/ActivityManager: Force stopping com.NSouth.NSouthApp appid=10459 user=0: clear data
01-11 21:38:10.251 3588-4061/? I/ActivityManager: Killing 19562:com.NSouth.NSouthApp/u0a459 (adj 0): stop com.NSouth.NSouthApp cause clear data
01-11 21:38:10.261 3588-4061/? W/ActivityManager: Force removing ActivityRecord{3f90827e u0 com.NSouth.NSouthApp/.Activity_Course t12626}: app died, no saved state
01-11 21:38:10.261 3588-4061/? V/ApplicationPolicy: isApplicationStateBlocked userId 0 pkgname com.NSouth.NSouthApp
01-11 21:38:10.261 3588-4061/? V/ApplicationPolicy: isApplicationStateBlocked userId 0 pkgname com.NSouth.NSouthApp
01-11 21:38:10.291 3588-4061/? I/ActivityManager:   Force finishing activity 3 ActivityRecord{3a98b6d4 u0 com.NSouth.NSouthApp/.Activity_Main t12626}
01-11 21:38:10.291 3588-4061/? V/ApplicationPolicy: isApplicationStateBlocked userId 0 pkgname com.NSouth.NSouthApp
01-11 21:38:10.311 3588-4061/? I/ActivityManager: Force stopping com.NSouth.NSouthApp appid=10459 user=0: clear data
01-11 21:38:10.311 3588-4061/? I/ActivityManager:   Force finishing activity 3 ActivityRecord{3a98b6d4 u0 com.NSouth.NSouthApp/.Activity_Main t12626 f}
01-11 21:38:10.311 3588-4061/? W/ActivityManager: Duplicate finish request for ActivityRecord{3a98b6d4 u0 com.NSouth.NSouthApp/.Activity_Main t12626 f}
01-11 21:38:10.321 3588-4061/? V/ApplicationPolicy: isApplicationStateBlocked userId 0 pkgname com.NSouth.NSouthApp
01-11 21:38:10.321 3588-4061/? V/ApplicationPolicy: isApplicationStateBlocked userId 0 pkgname com.NSouth.NSouthApp
01-11 21:38:10.461 3588-4343/? I/WindowState: WIN DEATH: Window{1847ccd8 u0 d0 com.NSouth.NSouthApp/com.NSouth.NSouthApp.Activity_Main}
01-11 21:38:10.531 3588-3784/? E/WindowState: getStack: Window{2ed8de84 u0 d0 com.NSouth.NSouthApp/com.NSouth.NSouthApp.Activity_AddCourse} couldn't find taskId=12626 Callers=com.android.server.wm.WindowState.getDisplayContent:1246 com.android.server.wm.WindowState.isDefaultDisplay:1936 com.android.server.wm.WindowState.getMultiWindowStyleLw:2520 com.android.internal.policy.impl.multiwindow.MultiPhoneWindowManager.shouldEnableLayoutInsetsBySoftInput:1601 
01-11 21:38:10.531 3588-3784/? E/WindowState: getStack: Window{2ed8de84 u0 d0 com.NSouth.NSouthApp/com.NSouth.NSouthApp.Activity_AddCourse} couldn't find taskId=12626 Callers=com.android.server.wm.WindowState.getDisplayContent:1246 com.android.server.wm.WindowState.isDefaultDisplay:1936 com.android.server.wm.WindowState.getMultiWindowStyleLw:2520 com.android.internal.policy.impl.multiwindow.MultiPhoneWindowManager.shouldEnableLayoutInsetsBySoftInput:1601 
01-11 21:38:10.711 20089-20089/? I/ClearDataReceiver: [#DCM#] Intent Data: package:com.NSouth.NSouthApp
01-11 21:38:10.781 20089-20089/? I/ClearDataReceiver: [#DCM#] Intent Data: package:com.NSouth.NSouthApp
01-11 21:38:10.821 3588-3784/? E/WindowState: getStack: Window{2ed8de84 u0 d0 com.NSouth.NSouthApp/com.NSouth.NSouthApp.Activity_AddCourse} couldn't find taskId=12626 Callers=com.android.server.wm.WindowState.getDisplayContent:1246 com.android.server.wm.WindowState.isDefaultDisplay:1936 com.android.server.wm.WindowState.getMultiWindowStyleLw:2520 com.android.internal.policy.impl.multiwindow.MultiPhoneWindowManager.shouldEnableLayoutInsetsBySoftInput:1601 
01-11 21:38:10.821 3588-3784/? E/WindowState: getStack: Window{2ed8de84 u0 d0 com.NSouth.NSouthApp/com.NSouth.NSouthApp.Activity_AddCourse} couldn't find taskId=12626 Callers=com.android.server.wm.WindowState.getDisplayContent:1246 com.android.server.wm.WindowState.isDefaultDisplay:1936 com.android.server.wm.WindowState.getMultiWindowStyleLw:2520 com.android.internal.policy.impl.multiwindow.MultiPhoneWindowManager.shouldEnableLayoutInsetsBySoftInput:1601 
01-11 21:38:11.211 20089-20089/? I/ClearDataReceiver: [#DCM#] Intent Data: package:com.NSouth.NSouthApp
01-11 21:38:11.251 16844-20183/? D/PackageBroadcastService: Received broadcast action=android.intent.action.PACKAGE_DATA_CLEARED and uri=com.NSouth.NSouthApp
01-11 21:38:11.261 16844-20183/? D/AccountUtils: Clearing selected account for com.NSouth.NSouthApp
01-11 21:38:11.291 16844-20183/? I/LocationSettingsChecker: Removing dialog suppression flag for package com.NSouth.NSouthApp
01-11 21:38:11.311 16844-17661/? I/Icing: doRemovePackageData com.NSouth.NSouthApp

更新

我学到了一些东西 .

  • 首先,BackupManagerService source code清楚地显示应用程序数据已清除,如果还原操作失败,应用程序将关闭 . (有关还原操作,请参阅 agentErrorCleanuphandleTimeout() . )

  • 其次,没有调用 MyBackupAgent 中的任何方法(调试日志没有被写入,也没有在断点处停止) . 换句话说,看起来我没有办法解决这个问题 .

所以... is this what we should expect if signatures don't match? 我想这不应该't happen in production, so maybe it'没关系......?

Update 2: 如果app 's backed up version is greater than the just-installed version. Again, shouldn' t在 生产环境 中发生,也会发生,但仍然有点难看 .

1 回答

  • 0

    问题是如果查看BackupManagerService代码,恢复超时为60秒 .

    如果还原超过60秒,则会失败 .

    MyBackupAgent中的方法未被调用,因为它们是另一个进程的一部分 . 调试代码的方法是记录消息(Log.v) .

    有同样的问题,尝试解压缩1MB文件,我的恢复也超时 . 我找到的解决方案是将文件解压缩到onRestore之外 .

    因此,尽可能保持您的onRestore精益 .

    class BackupManagerService extends IBackupManager.Stub {
        ...
    
    
        // Timeout interval for deciding that a bind or clear-data has taken too long
        static final long TIMEOUT_INTERVAL = 10 * 1000;
        // Timeout intervals for agent backup & restore operations
        static final long TIMEOUT_BACKUP_INTERVAL = 30 * 1000;
        static final long TIMEOUT_RESTORE_INTERVAL = 60 * 1000;
    

相关问题