-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Allow backups once again #16306
Comments
For Android auto backup the Firefox user profile would need to be audited. When this was enabled several years ago it corrupted profiles and Sync data. This would require a significant amount of work from people who have a strong knowledge of the Gecko profile, our Sync data stores and the Fenix data stores along with Android backup. |
You are supposed to use Firefox account now. It works well for me. Of course it stores everything on the cloud. |
Collections are not synced. If your device fails, your collections are gone. |
@jtagcat what are collections? Wasn't aware of such thing. |
Apps targeting Android 11 will not be able to disable device-to-device transfers of backup anyway [1]. Seems about time Fenix fixed profiles. [1] https://developer.android.com/about/versions/11/behavior-changes-11#device-to-device-file-transfer |
@ix5 99% of apps don't target Android 11, that would be great in 5 years. Even so, remains to be seen if ALL the data gets transferred, or parts of it at certain locations or specified on manifest whatnot. the iOS approach is perfect. |
essentially bookmark/tab groups (but not that great) |
Discussions going on in #18373 |
As far as I understand the subject feature will also allow tabs export (mean sessionstore.js or what file it is now). |
any updates on Collection sync? |
This issue is about backups. #4424 is about syncing collections. And no, there is no recent update. |
Just wanted to add, that Sync (on desktop at least) does not sync addons' data. For example, uBlock extension will be synced but its config won't be. As far as I'm aware, it's difficult to backup/restore addon data without getting your hands dirty. https://askubuntu.com/questions/141803/how-can-i-backup-installed-firefox-add-ons-and-restore On Android, this would be even more fiddly - most backup apps require ROOT access and Android doesn't have a solid backup/restore like iOS does. NewPipe (android youtube client) allows exporting/importing an .xml of your config (settings, subscriptions) to your file system, which is great. |
The only option to do it right is to root the device I'm afraid. |
Moved to bugzilla: https://bugzilla.mozilla.org/show_bug.cgi?id=1808763 Change performed by the Move to Bugzilla add-on. |
Accompanying issue to Pull #16305
What is the user problem or growth opportunity you want to see solved?
Users expect Android's backup and restore feature to "give them back" their app data upon migrating to a new device.
Rivaling browsers such as Chrome (or Safari on iOS) automatically carry over user data. This process seems seamless to the average user who does not know how tightly coupled Chrome's profiles are to a user's Google account ("Is just works" with Chrome).
Firefox Mobile currently just loses user data upon changing devices if not signed in to the sync service. The Mozilla-proprietary "sync" feature - which is heavily promoted - requires users to once again provide login data on their new devices and currently does not sync their collections (see #4424)
Technical
App developers can opt out of the Android backup system by setting
allowBackup=false
in their AndroidManifest.xml (see Enabling Auto-Backup ), as has been done for Fenix in 28ee6dd(Following discussion in #4072 )
The app data backup-restore mechanism serves two purposes:
Restore app data upon migration to a new device
For most Android devices, this will be done automatically via Google's "GMS backup transport", but others might implement their own backup transport.
See https://developer.android.com/guide/topics/data/testingbackup#HowBackupWorks
adb commands
Give agency to users to (partially) backup/restore application data via adb commands
Not everyone wants to use Mozilla's sync feature. When migrating devices (which is the most common usecase for Android's backup feature), the much better option is to have your settings and bookmarks "automagically" re-appear.
Also note: This does not have to clash with the Mozilla sync feature. It would be even better if the signed-in state of the Mozilla account was automatically restored with a migration as well.
How do you know that this problem exists today? Why is this important?
#4424
#2080 (and duplicates)
#417
Who will benefit from it?
Issues yet to fix
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: