Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add an option to disregard the `allowBackup` option for Android 12
See original GitHub issueAndroid 11 ignores the allowBackup manifest attribute for device to device transfers (https://developer.android.com/about/versions/11/behavior-changes-11#device-to-device-file-transfer). That means the local backup transport supports it in principle and the apps must support it in principle too. I think it would be a nice addition to Seedvault to make this behavior a (configurable) option. If this is indeed possible of course. This is partly related to #36.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:24
- Comments:33 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
The question is: should they? And who owns the data? I still don’t like the idea that an app tells me what I may gratefully backup and what not. On my Linux system, there are no such restrictions. And nobody would keep me from backing up even e.g.
/devor/proc. And no, I wouldn’t try restoring THAT from a backup either. If I would not know about such culprit, I’d expect a warning. But in the end I’d be the one to decide. Make it an advanced option in the “danger zone” if you like. Etc, I’ve already outlined it above 😉So if the user’s computer is compromised and they’ve whitelisted ADB access,
adb backupshould be able to steal all of their data?