adb restore failed to re-install apk [37130390]

Obsolete

Bug

[AOSP] assigned

Status Update

No update yet.

Description

ji...@gmail.com

created issue #1

Dec 19, 2016 03:30AM

Environment: Nexus 6P/7.1.1/NMF26F
HostPC: Windows 10
adb version:
Android Debug Bridge version 1.0.36
Revision 0e9850346394-android

- Steps to reproduce the problem (including sample code if appropriate).

1. make backup file.
>adb backup -f test -nosystem -noshared -apk com.example.testsurrogate

2. uninstall the app.
>adb uninstall com.example.testsurrogate

3. restore it.
>adb restore test

- What happened.
It seems that the device complete the process.
But backed up application was not restored.

- What you think the correct behavior should be.
The application was restored.

This is the logcat's output.

-------------
BackupManagerService: acknowledgeFullBackupOrRestore : token=974867546 allow=true
BackupManagerService: --- Performing full-dataset restore ---
BackupManagerService: Package com.example.testsurrogate not installed; requiring apk in dataset
BackupManagerService: APK file; installing
BackupManagerService: Installing from backup: com.example.testsurrogate
asset : Asset path /data/cache/backup_stage/com.example.testsurrogate is neither a directory nor file (type=0).
DefContainer: Failed to parse package at /data/cache/backup_stage/com.example.testsurro
gate: android.content.pm.PackageParser$PackageParserException: Failed to parse /data/cache/backup_stage/com.example.test
surrogate
BackupManagerService: [discarding file content]
BackupManagerService: Saw type=0 in tar header block, info=FileMetadata{null,0,null:,0}
BackupManagerService: Full restore processing complete.
bu : Finished.
-------------

If apk is already installed, adb restore works well.

In the case Android 6.0.1/Nexus5, I can restore this same backup file.

deleted

Restricted

0 B

Comments

am...@google.com <am...@google.com> Dec 19, 2016 07:22AM

Assigned to am...@google.com.

am...@google.com <am...@google.com> #2Dec 19, 2016 09:15AM

Although VPN connections under Android 7.1.2 worked for me, they do not work under Android 8.0.0 anymore. (IPSec Xauth PSK)

lo...@gmail.com <lo...@gmail.com> #3Dec 29, 2016 03:35PM

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

Steps to reproduce
What steps are needed to reproduce this issue?

Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)

Expected output
What is the expected output?

Current output
What is the current output?

Android bug report
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report file to this issue.

Alternate method:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.

lo...@gmail.com <lo...@gmail.com> #4Dec 29, 2016 03:45PM

Please provide the information requested in

comment #2

to investigate further.

do...@payjoy.com <do...@payjoy.com> #5Jan 2, 2017 12:06AM

Please provide the information requested in

comment #3

to investigate further.

ps...@gmail.com <ps...@gmail.com> #6Jan 5, 2017 09:15AM

Hi I Am experiencing the same issues as mentioned by the topic starter. I've tried to create a bug report, but i haven't rooted my device. However, i have attached the log of my VPN-router below.

Steps to reproduce
Configure a L2TP / IPsec PSK VPN using the native VPN client on Android 8 and try to connect

Frequency
Issue occurs 100% of the time.

Expected output
Connected to VPN

Current output
Message that connection failed.

Router log (IP-ADRES = the IP address of the Android)

2017-10-20 13:12:21 [IPSEC/IKE][Local][66:-][@IP-ADRES] may be security method/sbunet setting/GRE setting unmatched?
2017-10-20 13:12:21 [IPSEC/IKE][Local][66:-][@IP-ADRES] state transition fail: STATE_QUICK_R0
2017-10-20 13:12:19 sent MR3, ISAKMP SA established with IP-ADRES. In/Out Index: 66/0
2017-10-20 13:12:19 Matching General Setup key for dynamic ip client...
2017-10-20 13:12:19 NAT-Traversal: Using RFC 3947, no NAT detected
2017-10-20 13:12:19 Accept Phase1 prorosals : ENCR OAKLEY_AES_CBC, HASH OAKLEY_SHA
2017-10-20 13:12:19 Matching General Setup key for dynamic ip client...
2017-10-20 13:12:19 Find Phase1 proposal: SHA2_256
2017-10-20 13:12:19 Matching General Setup key for dynamic ip client...
2017-10-20 13:12:19 Find Phase1 proposal: SHA2_256
2017-10-20 13:12:19 Matching General Setup key for dynamic ip client...
2017-10-20 13:12:19 Matching General Setup key for dynamic ip client...
2017-10-20 13:12:19 Responding to Main Mode from IP-ADRES

Thanks for looking into this and good luck!

tg...@gmail.com <tg...@gmail.com> #7Jan 7, 2017 12:18AM

Steps to reproduce:
1. Setup VPN connection using IPSec Xauth PSK with IPSec key
2. Connect to VPN server
3. Connection attempt will fail

Frequency
100%

Expected output
Connect to VPN server successfully

Current output
Connection attempt fails

ps...@gmail.com <ps...@gmail.com> #8Jan 22, 2017 12:32PM

It works for me but only "non-permanent".

As soon as I actvate "permanent" it cant connect... like in 6.x and 7.x (now 8.0.0)

me...@gmail.com <me...@gmail.com> #9Feb 7, 2017 03:00AM

oh sry... its "Always On" in english version

mi...@gmail.com <mi...@gmail.com> #10Mar 5, 2017 02:20AM

comment #7

:
Can you please check whether issue is reproducible with latest Android 8.1.0 build(OPM1.1171019.011) for Pixel device?
If issue is still reproducible, please capture a bugreport and share it here.

[Deleted User] <[Deleted User]> #11Mar 20, 2017 09:00AM

Issue still reproducible with Android 8.1.0 build(OPM1.1171019.011) on Pixel device.

ma...@googlemail.com <ma...@googlemail.com> #12Mar 20, 2017 02:10PM

Could fix this issue now by removing the whole VPN user account and create a new one. Now the connection works again. As I'm not sure if I tried that with an earlier Android version I can only say that there must be at least an issue with my VPN system (AVM Fritz!Box 7490).

gb...@gmail.com <gb...@gmail.com> #13Apr 13, 2017 11:08PM

For anyone having similar issues, see my recent comments here

https://issuetracker.google.com/issues/37074640#comment366
I'm curious if these are related or if my case is unique. If possible run 'ifconfig' on the device while trying to connect and compare the MTU of the ppp0 interface with that of your main wifi/LTE interface

ma...@gmail.com <ma...@gmail.com> #14Apr 19, 2017 12:04PM

Thank you for your feedback. We assure you that we are doing our best to address the issue reported, however our product team has shifted work priority that doesn't include this issue. For now, we will be closing the issue as won't fix obsolete. If this issue currently still exists, we request that you log a new issue along with latest bug report here

https://goo.gl/TbMiIO.

me...@gmail.com <me...@gmail.com> #15Apr 19, 2017 12:55PM

To be clear, reinstalling the APK of the apps I attempted to restore did not result in a successful restoration of their data, either, so this suggested workaround does not work for me.

gb...@gmail.com <gb...@gmail.com> #16Apr 19, 2017 01:00PM

I have discovered that if you make a backup including the -noapk flag, you are able to install the apk using "adb install app.apk" and then restore from the backup.

You can still backup multiple (or all) apps and obb files do not cause an issue. You just need to make sure to install the apks before the restore.

co...@gmail.com <co...@gmail.com> #17May 7, 2017 09:54PM

How can this happen on a stable release? Google, pay more attention to this, you are making people lose data. Affected users use iPhone in the meanwhile, the backup feature of iTunes is far superior.

[Deleted User] <[Deleted User]> #18May 18, 2017 10:10AM

I think it is quite obvious. They don't prioritize this method of backup because they want us to backup our data using their cloud storage. Their business model is to make money by having our data...

an...@gmail.com <an...@gmail.com> #19Jul 2, 2017 09:31AM

Why on Earth isn't this bug resolved in Android 7.1.2?

07-02 08:48:52.772 30694 30707 W asset : Asset path /cache/backup_stage/lutey.FTPServer is neither a directory nor file (type=0).
07-02 08:48:52.773 30694 30707 W DefContainer: Failed to parse package at /cache/backup_stage/lutey.FTPServer: android.content.pm.PackageParser$PackageParserException: Failed to parse /cache/backup_stage/lutey.FTPServer
07-02 08:48:52.775 2834 31091 D BackupManagerService: [discarding file content]
07-02 08:48:52.775 2834 31091 W BackupManagerService: Saw type=0 in tar header block, info=FileMetadata{null,0,null:,0}
07-02 08:48:52.775 2834 3799 I BackupManagerService: Full restore processing complete.
07-02 08:48:52.772 30694 30707 W asset : Asset path /cache/backup_stage/lutey.FTPServer is neither a directory nor file (type=0).
07-02 08:48:52.773 30694 30707 W DefContainer: Failed to parse package at /cache/backup_stage/lutey.FTPServer: android.content.pm.PackageParser$PackageParserException: Failed to parse /cache/backup_stage/lutey.FTPServer
07-02 08:48:52.775 2834 31091 D BackupManagerService: [discarding file content]
07-02 08:48:52.775 2834 31091 W BackupManagerService: Saw type=0 in tar header block, info=FileMetadata{null,0,null:,0}
07-02 08:48:52.775 2834 3799 I BackupManagerService: Full restore processing complete.

The only workaround that I've found is installing the required app from Play Store/apk file, then stopping (!) it and cleaning its data (!) and then restoring it using "adb restore".

an...@gmail.com <an...@gmail.com> #20Jul 2, 2017 09:33AM

As far as I know Android 7.1 is a fully supported branch so this bug _must_ be fixed. It's core functionality because over 99% of apps in Play Store do _not_ support cloud backups.

[Deleted User] <[Deleted User]> #21Jul 11, 2017 09:09AM

I am guessing now, but I don't think this backup method is supposed to backup more than the cloud backups. If I am right, then the apps that don't support cloud backups also don't support this kind of backup.

ra...@gmail.com <ra...@gmail.com> #22Aug 1, 2017 05:40AM

If that's the case then I guess no apps support cloud backup because ADB restore restores absolutely nothing, it fails with PackageParserException on every single app.

sc...@yahoo.de <sc...@yahoo.de> #23Aug 8, 2017 08:39PM

This still hasn't been fixed after nearly an ENTIRE YEAR!!!
Seriously, what the hell are you doing Google???

de...@gmail.com <de...@gmail.com> #24Sep 24, 2017 06:03PM

Having run into the same problem, I'm thinking the same thing. How has this not been fixed?

an...@gmail.com <an...@gmail.com> #25Sep 24, 2017 06:20PM

> If I am right, then the apps that don't support cloud backups also don't support this kind of backup.

This is patently false. In fact this method existed long before Google enabled cloud backup and it still works.

db...@gmail.com <db...@gmail.com> #26Sep 24, 2017 07:57PM

Can u take this off my email the traker danuelpaschal62@gmail.com

ja...@gmail.com <ja...@gmail.com> #27Dec 26, 2017 08:52AM

Shame on Google! It happens on all of the new devices.
Google cloud backup works like for 5% of apps and the adb solution does not work either.
This is insane

ap...@gmail.com <ap...@gmail.com> #28Jun 13, 2018 09:26PM

We're also victims of this issue. Please fix.

al...@google.com <al...@google.com> #29May 13, 2019 09:15AM

Status: Won't Fix (Obsolete)

adb backup and restore has now been deprecated.

https://support.google.com/android/answer/2819582?hl=en-GB contains information on how to backup and restore information from your device, if an application is not backing up the data you feel it should please contact the application developer and ask how they can support what you need.

[Deleted User] <[Deleted User]> #30May 13, 2019 10:13AM

Wow. So what I'm hearing is "we don't support doing backups. if you want your data to be safe, don't use android".

an...@gmail.com <an...@gmail.com> #31May 13, 2019 10:57AM

The only way to make Google change their mind is to give this issue as much publicity as possible everywhere: reddit/twitter/news websites/etc. etc. etc.

Maybe we should ask Engadget/The Verge/other media to approach Stephanie Cuthbertson and ask her why this decision has been taken and if Google might want to reconsider it.

Bug tracker is not a public discussion forum and comments like yours will only make Google employees close this ticket.

[Deleted User] <[Deleted User]> #32May 13, 2019 10:58AM

"Bug tracker is not a public discussion forum and comments like yours will only make Google employees close this ticket."

...as opposed to... working on the problem?

an...@gmail.com <an...@gmail.com> #33May 13, 2019 01:07PM

The decision has already been made and no one is working on the problem. This bug report is CLOSED as WON'T FIX.

The only thing we can do is making Google aware that this feature is extremely necessary for a lot of people.

al...@google.com <al...@google.com> #34May 13, 2019 03:49PM

The re-installation of APKs from a backup was purposely disabled in Android P (

https://android.googlesource.com/platform/frameworks/base/+/7323eecba36991e161d621c001d35e8cccb258ab). Given that we are deprecating adb backup and restore it is unlikely to be re-instated.