Closed grote closed 2 months ago
@grote this seems to have a merge conflict but seems good otherwise.
Quite interested in how Google's backup service handles this one.
Regardless, still worth preventing this from happening in subsequent backups..
Quite interested in how Google's backup service handles this one.
Me too. Actually, with my test app https://gitlab.com/grote/backupagentcrasher we should be able to find out. Maybe @t-m-w still has a stock phone to try?
just rebased and pushed
Quite interested in how Google's backup service handles this one.
Me too. Actually, with my test app https://gitlab.com/grote/backupagentcrasher we should be able to find out. Maybe @t-m-w still has a stock phone to try?
Stock fails on the crasher and the whole process is interrupted, just as with Seedvault. A toast appears with the message: "Couldn’t back up data. Try again later." 37 apps are backed up. Try again, same thing. If I uninstall the crasher and try again, there is no error, and 39 apps are backed up.
wow thanks for testing! backup DoS app here we come! Nice we are even going beyond play services here.
Nice find. Wonder if we can report this upstream somehow.
Nice find. Wonder if we can report this upstream somehow.
issuetracker.google.com :)
This can happen when the app process gets killed while its BackupAgent is running. There are several qcom apps in the wild that have this issue. These are DoSing our backups and are non-free, so we are defending ourselves against them.
Fixes #491