While developing a new home panel layout that required a database migration, I noticed that the migration code inside HomeProvider.jsm is only lazily triggered when an addon is actively using a database connecting (getDatabaseConnection()). The Java code that is building the panel UI does not trigger the migration and therefore has to be backwards compatible across all schema versions (theoretically). This adds some complexity. We could: * Trigger the migration from the Java side too. That's probably rather complex. * Perform the migration not lazily but as soon as HomeProvider.jsm is loaded (potential race condition?).

We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.