It's been a couple weeks since the last email on this thread. Does that
mean we're agreed on disabling auto-backup and doing it quickly?

On Wed, Oct 14, 2015 at 5:49 AM, Sebastian Kaspari <[email protected]>
wrote:

> I agree that disabling auto-backup (and with that also `adb backup` as it
> seems) is currently the best way forward - even though I like the idea of
> restoring the sync account.
>
> 1) I was looking for quick wins here like "add file X and user has benefit
> Y".
> 2) Right now I do not have much time to investigate all edge cases of
> things like (partially) restored accounts
> 3) I'd like to move fast here in order to get us into a state where we can
> set targetSdkVersion to 23 (by default this is the opt-in into auto backup)
>
> We can file follow-up bugs for investigating things like restoring
> accounts or (gecko) preferences. I think they could be mentor bugs for
> volunteers who are looking for a more "here be dragons" challenge (?).
>
>
> On Tue, Oct 13, 2015 at 11:08 PM, Mark Finkle <[email protected]> wrote:
>
>> As much as I like to think of ways to use new gizmos, I think the safest,
>> simplest way forward is to just disable the auto-backup feature. Allowing
>> any part of the data to be backed up and restored means we need to make
>> sure nothing breaks. Given we have lots of other work to do, I don't see a
>> need to go down the auto-backup road right now.
>>
>> On Mon, Oct 12, 2015 at 2:46 PM, Michael Comella <
>> [email protected]> wrote:
>>
>>> To recount today's Frontend meeting, we briefly spoke about conflict
>>> between Firefox Sync & auto backup. We came up with the possibility of
>>> syncing the Firefox Account Android-account so that when users switch to a
>>> different device, Sync will be automatically set up and the Firefox Sync
>>> services can restore the user's synced data (e.g. this could help
>>> differentiate Firefox and maintain retention on new devices). It's unclear
>>> if Firefox Sync will allow us to do that under the hood, but it's open to
>>> be investigated.
>>>
>>> We didn't discuss other data to potentially store – files, databases,
>>> and shared preferences, as Sebastian mentions above.
>>>
>>> I personally think it'd be great to save preferences as well, though I'm
>>> unsure how this could affect the Gecko-related preferences. However, I
>>> think with a bit of work, we could get preference sync working properly for
>>> preferences in the Android UI (e.g. mirror the prefs in shared preferences
>>> so Android can restore them). I think this is lower priority than the
>>> account work.
>>> - Mike
>>>
>>> On Mon, Oct 12, 2015 at 1:57 AM, Sebastian Kaspari <[email protected]>
>>> wrote:
>>>
>>>> Hey everyone!
>>>>
>>>> I have been looking into bug 1190375 [1] - "Create whitelist (or
>>>> blacklist) for Android Auto Backup" and need some input from you!
>>>>
>>>> Background:
>>>> * Android 6.0 automatically creates backups of application data and
>>>> accounts (for apps with targetSdkVersion >= 23)
>>>> * When the app is (re-) installed Google will download and restore
>>>> application data from the backup
>>>> * The backup is independent from the device. Switching to a new device
>>>> will restore the backup from a previous device.
>>>> * Each app can store up to 25 MB
>>>>
>>>> https://developer.android.com/training/backup/autosyncapi.html
>>>>
>>>> We want to create a whitelist of things that Google can safely backup
>>>> and restore across devices. But what should we add? My first intention was
>>>> to add our preferences to that whitelist. But some of them are actually
>>>> Gecko-related things and not just simple shared preferences.
>>>>
>>>> So what should we add? Files, databases and shared preferences are good
>>>> candidates.
>>>>
>>>> Sebastian
>>>>
>>>> [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1190375
>>>>
>>>> _______________________________________________
>>>> mobile-firefox-dev mailing list
>>>> [email protected]
>>>> https://mail.mozilla.org/listinfo/mobile-firefox-dev
>>>>
>>>>
>>>
>>> _______________________________________________
>>> mobile-firefox-dev mailing list
>>> [email protected]
>>> https://mail.mozilla.org/listinfo/mobile-firefox-dev
>>>
>>>
>>
>
> _______________________________________________
> mobile-firefox-dev mailing list
> [email protected]
> https://mail.mozilla.org/listinfo/mobile-firefox-dev
>
>
_______________________________________________
mobile-firefox-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/mobile-firefox-dev

Reply via email to