> that wouldn't account for background kills that's ok - we always startup correctly - the issue is when we start a "flow" but it never stops. > maybe this is something that we can cover with FXA-11915? This should just be a mobile impl of bug 1990334? But more generally, you are correct in that this can only be a "best effort". eg, moving to a "real" tab would make this worse in that the tab's happily waiting for you, but you forgot it. I think ultimately "authenticating" etc isn't an actual "account state", but somehow a "ui state" which somehow magically interacts with the "account state" something something :)
Bug 2030890 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
> that wouldn't account for background kills that's ok - we always startup correctly - the issue is when we start a "flow" but it never stops. > maybe this is something that we can cover with FXA-11915? This should just be a mobile impl of bug 1990334? But more generally, you are correct in that this can only be a "best effort". eg, moving to a "real" tab would make this worse in that the tab's happily waiting for you, but you forgot it. I think ultimately "authenticating" etc isn't an actual "account state", but somehow a "ui state" which somehow magically interacts with the "account state" something something :)
> that wouldn't account for background kills that's ok - we always startup correctly - the issue is when we start a "flow" but it never stops. > maybe this is something that we can cover with FXA-11915? That should just be a mobile impl of bug 1990334? But more generally, you are correct in that this can only be a "best effort". eg, moving to a "real" tab would make this worse in that the tab's happily waiting for you, but you forgot it. I think ultimately "authenticating" etc isn't an actual "account state", but somehow a "ui state" which somehow magically interacts with the "account state" something something :)