[HybridApp] Crash occurring at authenticate

[mateuuszzzzz]

Issues in authenticate lead to SIGABRT crash

https://console.firebase.google.com/project/expensify-mobile-app/crashlytics/app/android:org.me.mobiexpensifyg/issues/85c581edcdb39b941df627e7b1324a71?time=1740700800000:1741910399000&sessionEventKey=67cefafa008400013d9ebce8f0e5b943_2058637762788506650&types=crash

Logs:

authenticate.log

[melvin-bot]

Triggered auto assignment to @MitchExpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[mountiny]

Discussing here https://expensify.slack.com/archives/C08CZDJFJ77/p1741953203133269?thread_ts=1741905139.377289&cid=C08CZDJFJ77 might have to be handled by Callstack or SWM as they have access to the firebase

[mallenexpensify]

@mountiny and @mateuuszzzzz

1. What status do you think this issue is? (see below)
2. I see many more issues linked here and here (same thread for both), should I make those the same status as this?

Thx

• CRITICAL - UX Reliability, API Reliability and Performance bugs that are noticeable for a majority of users
• HIGH -  UX Reliability, API Reliability and Performance issues that are part of main flows and affect a subset of users
• MEDIUM - Debugging Tools to help make fixing existing bugs easier and getting fixes to customers faster and Architectural Improvements to the underlying framework and design of the app to improve performance, scalability, and maintainability
• LOW - Not very noticeable UX Reliability, API Reliability or Performance issues that only affect a single user or subset of users

[mateuuszzzzz]

@mallenexpensify I would keep all issues that are not single or sporadic occurrences as HIGH. In remaining cases I would change it to LOW cc: @mountiny