I no-op in the case of horrible network failure instead of throwing up what I thought would be alarming login errors on the assumption that network failures would happen, but infrequently.
This seems to not be the case.
Failure to obtain FxA login configuration should fire an ACRA log as well as display an android Toast to alert the user that FxA could not be reached.
@popey on twitter says the FxA login does nothing a lot. 8 times in a row.
https://twitter.com/popey/status/722452112630816768
I no-op in the case of horrible network failure instead of throwing up what I thought would be alarming login errors on the assumption that network failures would happen, but infrequently.
This seems to not be the case.
Failure to obtain FxA login configuration should fire an ACRA log as well as display an android Toast to alert the user that FxA could not be reached.