b26ac51e90
Problem was that we were trying to process menu changes (in response to account manager events) on some background thread as that's what account manager emits them on, so some code internally in PopupWindow's dismiss handling (i think, didn't dig very deeply here) was silently giving up and we'd get into a bad state. The reason this seemingly only happened if you quickly opened a menu on startup is because account manager isn't initialized until sometime after the startup finished. So the trick was to open the menu (and register account manager state callbacks) before it got initialized, so that the callbacks are invoked. This should also reproduce in other, much more obscure ways, e.g. if you open the menu right before sync is scheduled to run in the background, change FxA password on another connected client, and then eventually receive a onAuthenticationProblem callback. |
||
|---|---|---|
| .. | ||
| androidTest | ||
| debug | ||
| fenixBeta/res | ||
| fenixNightly | ||
| fennecBeta/res | ||
| fennecNightly/res | ||
| fennecProduction/res/xml | ||
| geckoBeta/java/org/mozilla/fenix/engine | ||
| geckoNightly/java/org/mozilla/fenix/engine | ||
| main | ||
| migration | ||
| test | ||