onWindowFocusChanged isn't designed to be used for application initialization. IIRC, we use it because it happens later in startup and allows us to show an empty window more quickly; however, the docs say that it is "managed independently of activity lifecycles" and apps "should not rely on any particular order between the callbacks here and those in the other lifecycle methods" (http://developer.android.com/reference/android/app/Activity.html#onWindowFocusChanged%28boolean%29). We should simply do initialization in onCreate(): onCreate is fired exactly once, and it's the intended hook for initialization.
I tried simply moving the initialize() call, but that did not work: https://tbpl.mozilla.org/?tree=Try&rev=7c81292ec94a
The patch bug 966788 comment 138 landed an increased wait time for Gecko:Ready - we should probably revert that back once this bug is solved.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1085591
No longer blocks: 1138529
You need to log in before you can comment on or make changes to this bug.