Skip to main content

onRestore not invoked for my custom BackupAgent



There are some data in my Android app that I would like to backup and restore. For that purpose I have created a custom implementation of BackupAgent.





In my manifest in have included the backup agent as you can see below







<manifest xmlns:android="http://schemas.android.com/apk/res/android"

android:installLocation="auto"

package="com.myapp"

android:versionCode="14"

android:versionName="1.13" >



<application

android:backupAgent="com.myapp.MyBackupAgent">



<meta-data

android:name="com.google.android.backup.api_key"

android:value="my key" />







I have included the backup service api key, although I am testing with the emulator (Android 2.2) and it should not be necessary, because it uses the local backup transport.





In order to do the test of the backup and restore I have done the following:





  • Start the emulator with my application installed.







  • Enable backup





    adb shell bmgr enable true









  • Call the part of my code were the dataChanged method in the BackupManager class is called.









  • Initiate manually the backup operation





    adb shell bmgr run









  • Checked in the log that the onBackup method of my custom BackupAgent was called.





  • Uninstall the app



  • Reinstall the app



  • Check in the log if the onRestore method is called.







The thing is that the onRestore method does not seem to be called and I don't know why. After reinstalling the app or manually triggering the restore with adb I see the following in the console.







$adb shell bmgr restore com.myapp

restoreStarting: 2 packages

restoreFinished: 0

done







and this other in the log







D/AndroidRuntime( 8259):

D/AndroidRuntime( 8259): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<

D/AndroidRuntime( 8259): CheckJNI is ON

D/AndroidRuntime( 8259): --- registering native functions ---

D/BackupManagerService( 59): MSG_RUN_RESTORE observer=android.app.backup.IRestoreObserver$Stub$Proxy@450e16a8

V/LocalTransport( 59): start restore 1

V/LocalTransport( 59): nextRestorePackage() = @pm@

V/LocalTransport( 59): getRestoreData() found 7 key files

V/LocalTransport( 59): ... key=com.android.providers.settings size=1208

V/LocalTransport( 59): ... key=com.myapp size=501

V/LocalTransport( 59): ... key=android size=1208

V/LocalTransport( 59): ... key=com.android.providers.userdictionary size=1208

V/LocalTransport( 59): ... key=com.android.browser size=1208

V/LocalTransport( 59): ... key=com.android.inputmethod.latin size=1208

V/LocalTransport( 59): ... key=@meta@ size=11

V/LocalTransport( 59): no more packages to restore

V/LocalTransport( 59): finishRestore()

V/LocalTransport( 59): finishRestore()

D/AndroidRuntime( 8259): Shutting down VM







but I don't see that the call to onRestore is actually made (I have some logging statements just at the beginning of it?





Has this ever happen to you? Is there any reason by the onRestore method is not called, even in the onBackup was called?





Thanks for your help!


Comments

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex