Install Nightly and start it
not crash
crashes
Could you share the top crash report from about:crashes?
logcat? https://github.com/mozilla-mobile/fenix/wiki/Logging-Crash-Information#using-adb-logcat-to-get-crash-information
same issue here after wasting 3 hours of my spare time it turns out that the crash occurs only if nighlty is set as default browser clearing default for browser in android setting solve the issue.
Could someone who is experiencing this please link a crash report from about:crashes 🙏
Hm cc @boek @eliserichards looks related to https://github.com/mozilla-mobile/fenix/pull/14126 possibly?
@ale82to that's correct! I removed it from default browser and it works.
I don't have google play installed, not sure if it is relevant.
secret settings looks odd

Clicking on prompt for review crashes.
54837620-7a09-43aa-ba65-0e63abb33cb1
com.google.android.play.core.internal.aq:/ailed to bind to the service.
com.google.android.play.core.internal.aq: Failed to bind to the service.
at com.google.android.play.core.internal.ap.a(Unknown Source:78)
at com.google.android.play.core.internal.ai.a(Unknown Source:4)
at com.google.android.play.core.internal.ag.run(Unknown Source:0)
at android.os.Handler.handleCallback(Handler.java:873)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:193)
at android.os.HandlerThread.run(HandlerThread.java:65)
I pressed on prompt to review earlier today, it crashes but I can restart the browser. Then it worked for few hours, and suddenly, without changing any settings it crashed.
So it worked for two days but now I get crash on startup with today builds, but not from the beginning (I mean right after the update).
I can't even open it if I change default browser / open via a link (I could with the original bug report) then I don't know if it is related, but I can't open about:crashes anyway
@B0pol That is very likely #14486 and unrelated to this issue.
I think we can close this crash.
No startup crash in Nightly 9/1 and RC 80.1.2, following the steps mentioned here: default browser and restart the app on a device without GPS.
Most helpful comment
I think we can close this crash.