It turns out the solution to this problem is that developers need to register for an API key for Google's backup transport, which can be done here <http://developer.android.com/guide/topics/data/ backup.html#BackupKey>.
The JavaDocs for implementing a BackupManager <http:// developer.android.com/reference/android/app/backup/BackupManager.html> make no mention of needing an API key or the associated Android Manifest metadata, which makes this problem non-obvious. On Sep 17, 6:13 pm, Carter <ccjerni...@gmail.com> wrote: > I have encountered a problem with the BackupManager introduced in > Android 2.2: I took the Backup/Restore example project included with > the SDK, built an APK signed with a debug key, and loaded it onto both > a Droid and Nexus One running Android 2.2. Then I ran "adb shell bmgr > backup com.example.android.backuprestore; adb shell bmgr run". I > immediately saw the following line in logcat: E/ > BackupTransportService( 1101): IGNORING BACKUP DATA without API key: > com.example.android.backuprestore > > When I tried uninstalling and reinstalling the sample application, its > data was not restored automatically. In addition, running "adb shell > bmgr restore com.example.android.backuprestore" did not restore the > data. > > When I repeated the process on an emulator running Android 2.2, it > worked perfectly. > > Why would this fail on the device but work on the emulator? Has > anyone else run into this issue? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
