1988212 - IllegalStateException: You need to call PushProcessor.install() on your Push instance from Application.onCreate().

Status: RESOLVED FIXED

(Firefox for Android :: Push, defect)

Description

[Matt Tighe [:matt-tighe]]

Seeing some Sentry reports spike for this

Comment 1

[Matt Tighe [:matt-tighe]]

Of the off chance this is related to our startup path changing due to the Startup Crash Activity, it could also potentially be impacting bug 1988188. Normally NSS initializes here

Comment 2

[Robert Kaiser]

On my Nightly (Fairphone 5, Android 15), I'm seeing this and java.lang.IllegalThreadStateException: Expected thread 2 ("main"), but running on thread 56 ("DefaultDispatcher-worker-2") (with various values of the thread and worker numbers, so if others are seeing this as well, that won't spike as much as it's spread over multiple signatures) quite a bit recently. Interestingly, this often happens when I'm entering other applications that have a password-like field, like my banking app that wants me to confirm something with a PIN entry.
If there's anything I can do to provide some info without investing tons of time, I'm happy to help.

Comment 3

[Segun Famisa [:segun]]

(In reply to Robert Kaiser from comment #2)

On my Nightly (Fairphone 5, Android 15), I'm seeing this and java.lang.IllegalThreadStateException: Expected thread 2 ("main"), but running on thread 56 ("DefaultDispatcher-worker-2") (with various values of the thread and worker numbers, so if others are seeing this as well, that won't spike as much as it's spread over multiple signatures) quite a bit recently. Interestingly, this often happens when I'm entering other applications that have a password-like field, like my banking app that wants me to confirm something with a PIN entry.
If there's anything I can do to provide some info without investing tons of time, I'm happy to help.

Thank you for your comment. Do you know specifically which crash you experience in this scenario you described? And are you using Firefox as your system-wide password manager? :

Interestingly, this often happens when I'm entering other applications that have a password-like field, like my banking app that wants me to confirm something with a PIN entry.

Comment 4

[Segun Famisa [:segun]]

I have been able to reproduce this issue in one way. I can't say for sure if this is the only way it is reproducible, but I can say it is one of the ways.

1. Set up Firebase push in debug builds
2. Sign-in to Firefox account
3. Enable debug drawer and use the crash debug tools to simulate a "startup crash"
4. Relaunch the app - you should land in the "recovery/crash mode"
5. Send a tab from another device to your test device while in this mode
6. You should expect the crash with this stack trace.

It seems that this is caused by a partial re-initialization after an early crash, and is related to the new startup crash detection flow. It seems it may be fixed by the work in bug 1992494

Comment 5

[Robert Kaiser]

(In reply to Segun Famisa [:segun] from comment #3)

Thank you for your comment. Do you know specifically which crash you experience in this scenario you described? And are you using Firefox as your system-wide password manager? :

I'm not exactly sure as my about:crashes listed both of those close to each other when I created the comment. I think the one in this bug (You need to call PushProcessor.install()…) is what happened in the cases I described here, as I saw this over and over for some time frame, while the other may be a startup crash on the restart or so, I only had that on Sep 30 right after but in the same minute as the other. And yes, I'm using Firefox as my system-wide password manager on this FP5 phone. All that said, I haven't seen those crashes after Sep 30 so far (and sorry, that's why I'm also only replying today, I was waiting to see if I encounter the crashes again) - knock on wood that they are gone... ;-)

Comment 6

[Jeff Boek [:boek]]

This should be fixed with bug 1992494