1794213 - org.mozilla.fenix.components.AbnormalFxaEvent$MissingExpectedAccountAfterStartup INFO

Status: REOPENED

(Firefox for Android :: Accounts and Sync, defect, P3)

Description

[Jonathan Almeida [:jonalmeida]]

From github: https://github.com/mozilla-mobile/android-components/issues/5050.

Seen while looking at Socorro nightly Fenix crashes. Apologies if this is the wrong place.

• Sample crash report: https://crash-stats.mozilla.com/report/index/f7e8bce2-5b35-4b6e-90c9-6e4710191113

• Currently the #4 overall top crash on Fenix nightly: https://crash-stats.mozilla.com/topcrashers/?product=Fenix&version=72.0a1&process_type=any

┆Issue is synchronized with this Jira Task

Change performed by the Move to Bugzilla add-on.

Comment 1

[Chris Peterson [:cpeterson]]

No recent crash reports

Comment 2

[Chris Peterson [:cpeterson]]

Reopening because this bug is about a non-fatal "INFO" reported to Sentry, not an exception. We received 36K reports from 24K Nightly + Beta users over the last seven days.

This is an old issue. It was first filed in A-C's GitHub issue tracker back in 2019: https://github.com/mozilla-mobile/android-components/issues/5050

https://sentry.io/organizations/mozilla/issues/3150561695

AbnormalFxaEvent$MissingExpectedAccountAfterStartup INFO from:

org.mozilla.fenix.components.AccountAbnormalities in onReady at line 47
mozilla.components.service.fxa.manager.FxaAccountManager$start$2$1 in invoke at line 14
mozilla.components.support.base.observer.ObserverRegistry in notifyObservers at line 31
mozilla.components.service.fxa.manager.FxaAccountManager in notifyObservers at line 7
mozilla.components.service.fxa.manager.FxaAccountManager$start$2 in invokeSuspend at line 51
kotlin.coroutines.jvm.internal.BaseContinuationImpl in resumeWith at line 9
kotlinx.coroutines.DispatchedTask in run at line 107
java.util.concurrent.ThreadPoolExecutor in runWorker at line 1167
java.util.concurrent.ThreadPoolExecutor$Worker in run at line 641
java.lang.Thread in run at line 919

Comment 3

[Mark Hammond [:markh] [:mhammond]]

FWIW, I was tracking down some other issue and saw this pop up for a user which was failing in various components due to no disk space left, which seems like a plausible explanation for this - eg, you could imagine we tried to save the account info, swallowed an exception due to a lack of disk space, then we act all surprised when we can't find the account info later.