[Awaiting payment 2026-01-23] [$125] Always unlock the network queue on auth errors and log the error

[mountiny]

Coming from here

If Authenticate throws an unexpected error, the network queue can remain locked for the rest of the session. In this state, all API calls stop working and the app can effectively be broken until the user force-quits it.
This failure is currently silent- so from our perspective it just looks like “the network stopped working.”
By handling the Auth call in a catch, we can:

• Always unlock the network queue on error, ensuring the app continues to work
• Track this error in Sentry
• Log it for easier debugging

Issue Owner

Current Issue Owner: @heyjennahay

[melvin-bot]

Triggered auto assignment to @heyjennahay (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.

[melvin-bot]

@rinej Whoops! This issue is 2 days overdue. Let's get this updated quick!