1. 25 Aug, 2020 2 commits
  2. 13 Aug, 2020 1 commit
  3. 30 Jul, 2020 1 commit
    • Grisha Kruglov's avatar
      Bump 'settings' migration version to re-run it · bc809cdb
      Grisha Kruglov authored
      We retain Fennec's preferences on disk, so re-running this migration will
      make sure that marketing/experiments settings in Fenix correspond to the FHR setting
      in Fennec (they'll be turned off if FHR settings is 'off', and left 'on' if FHR is 'on').
      
      For the users running this migration for the first time, it's just a regular migration.
      
      For the users who already ran this migration, we will re-align data collections settings around
      their choices in Fennec.
      bc809cdb
  4. 29 Jul, 2020 1 commit
  5. 13 May, 2020 1 commit
    • Grisha Kruglov's avatar
      Initialize accountManager on the main thread during migration · 09b55546
      Grisha Kruglov authored
      This fixes fallback from https://github.com/mozilla-mobile/android-components/pull/6395 in which
      FennecMigrator changed to accept a Lazy-wrapped reference to the account manager.
      
      This was done so that during regular (non-migrating) startup, a simple act of building a no-op
      migrator will not cause account manager initialization.
      
      However, during a migrating startup this creates a race to initialize account manager.
      Two participants in this race are:
      1) FenixApplication running expensive operations (such as storage init, account manager init)
      after visual completeness. However, currently that just entails a 5 second delay from `onStart`.
      2) FxA migration, which runs roughly at the mid-point of the migration.
      
      Account manager currently can't be initialized on a background thread (or it will crash).
      FxA migration runs on a background thread, so if (2) wins (that is, migrations before FxA migration take
      less than 5 seconds), then migration will crash.
      
      This patch adds an eager initialization right before we kick-off migrations but are still on the main thread,
      iff an FxA migration will be executed.
      09b55546
  6. 08 May, 2020 1 commit
  7. 01 Apr, 2020 1 commit
  8. 26 Mar, 2020 1 commit
  9. 23 Mar, 2020 1 commit
  10. 10 Mar, 2020 1 commit
  11. 03 Mar, 2020 1 commit
    • Grisha Kruglov's avatar
      Closes #5715: Login storage refactor · aa9a36aa
      Grisha Kruglov authored
      This refactor changes how (most) consumers are expected to interact with the logins storage.
      Instead of "locking"/"unlocking" the store whenever its needed, a connection to a storage
      layer is now cached on first access and re-used for subsequent operations.
      
      Various components relying on logins storage have been simplified.
      aa9a36aa
  12. 14 Feb, 2020 1 commit
  13. 10 Feb, 2020 1 commit
    • Andrei Lazar's avatar
      Fix for #5603 - Implement notification for when the migration is complete · 0e3d4238
      Andrei Lazar authored
      Currently a notification is being shown for migration progress status, but no notification is being
      displayed to the user for when the migration is complete.
      In order to properly handle this notification's remove or click action, a broadcast receiver is
      required that listens for this specific actions so it can remove the notification's channel.
      0e3d4238
  14. 09 Feb, 2020 1 commit
  15. 06 Feb, 2020 1 commit
  16. 05 Feb, 2020 2 commits
  17. 04 Feb, 2020 1 commit
  18. 22 Jan, 2020 2 commits
  19. 20 Jan, 2020 1 commit
  20. 15 Jan, 2020 3 commits
  21. 14 Jan, 2020 3 commits
  22. 09 Jan, 2020 2 commits
  23. 07 Jan, 2020 1 commit
  24. 19 Dec, 2019 1 commit
  25. 18 Dec, 2019 1 commit
  26. 10 Dec, 2019 1 commit
    • Mugurell's avatar
      For #5267 - Migrate telemetry setting · 2b1b3479
      Mugurell authored
      
      
      This patch introduces a new "FennecSettingsMigrator" which will be responsible
      for migrating all common Fennec - Fenix settings.
      
      Starting with the telemetry opt-in status which in Fenix will be "true" if the
      Firefox Health Report setting ws also true on Fennec, and "false" otherwise.
      It may be possible that the Fenix install is a new one and not an upgrade from
      Fennec in which case no setting will be migrated and the migration would be
      considered as successful.
      Co-authored-by: default avatarGrisha Kruglov <gkruglov@mozilla.com>
      2b1b3479
  27. 07 Dec, 2019 1 commit
  28. 25 Nov, 2019 1 commit
  29. 19 Nov, 2019 1 commit
  30. 17 Nov, 2019 1 commit
    • Grisha Kruglov's avatar
      Closes #5063: don't log unneccessary illegal state exceptions · c3236356
      Grisha Kruglov authored
      We are logging exceptions when no profile is found, which is actually a legit case.
      There will be no profile on a fresh install, for example.
      
      This patch makes these kinds of exceptions more precise/useful: we'll only send a report
      in case there's a profile but a missing dbPath. We'll now also send an exception in case
      of an IOException while parsing profiles.
      c3236356
  31. 13 Nov, 2019 1 commit
  32. 31 Oct, 2019 1 commit
    • Grisha Kruglov's avatar
      Fennec FxA state migration · 63f9fdc8
      Grisha Kruglov authored
      This adds basics of the Fennec Firefox Account state migration, bailing
      out if we're not processing v4 fxa state.
      
      Migration is done from the "pickle file". Cleaning up system account is TBD.
      63f9fdc8