This repository has been archived by the owner on Nov 1, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 475
Fennec migration: run in a foreground service #4879
Labels
Milestone
Comments
@grigoryk Are you working on this? Otherwise I may pick that up. :) |
pocmo
added a commit
to pocmo/android-components
that referenced
this issue
Nov 25, 2019
pocmo
added a commit
to pocmo/android-components
that referenced
this issue
Nov 26, 2019
pocmo
added a commit
to pocmo/android-components
that referenced
this issue
Nov 27, 2019
pocmo
added a commit
to pocmo/fenix
that referenced
this issue
Dec 9, 2019
In order to avoid a half done migration we are moving the migration to a background service (that is running the "foreground"). This is the Fenix part of: mozilla-mobile/android-components#4879
pocmo
added a commit
to pocmo/fenix
that referenced
this issue
Dec 9, 2019
In order to avoid a half done migration we are moving the migration to a background service (that is running in the "foreground"). This is the Fenix part of: mozilla-mobile/android-components#4879
grigoryk
pushed a commit
to pocmo/fenix
that referenced
this issue
Dec 10, 2019
In order to avoid a half done migration we are moving the migration to a background service (that is running in the "foreground"). This is the Fenix part of: mozilla-mobile/android-components#4879
bors bot
pushed a commit
to mozilla-mobile/fenix
that referenced
this issue
Dec 10, 2019
7034: Run migration in background service. r=grigoryk a=pocmo In order to avoid a half done migration we are moving the migration to a background service (that is running in the "foreground"). This is the Fenix part of: mozilla-mobile/android-components#4879 Co-authored-by: Sebastian Kaspari <s.kaspari@gmail.com>
pocmo
added a commit
to pocmo/fenix
that referenced
this issue
Dec 10, 2019
In order to avoid a half done migration we are moving the migration to a background service (that is running in the "foreground"). This is the Fenix part of: mozilla-mobile/android-components#4879
pocmo
added a commit
to mozilla-mobile/fenix
that referenced
this issue
Dec 10, 2019
In order to avoid a half done migration we are moving the migration to a background service (that is running in the "foreground"). This is the Fenix part of: mozilla-mobile/android-components#4879
Just landed in Fenix and should go into the next builds. |
A-C: Android Components Sprint Planning
automation
moved this from 🏃♀️ In Progress
to 🏁 Done
Dec 10, 2019
Verified as fixed on Release, Beta, Nightly 12/13 migration builds with Pixel 3a XL (Android 10), Samsung Galaxy S8 (Android 9), Huawei Honor 8 (Android 7.0). |
sblatz
pushed a commit
to sblatz/android-components
that referenced
this issue
Dec 19, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Related to #4872 - our migrations are potentially slow, which creates a large window of time for things to go wrong (OS killing us, user killing us, some bad interaction with Fenix occuring, etc).
To get an additional margin of safety, we could wrap our migration code in a foreground service.
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: