You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-10-05] Log the reason for every sign-out #102131
Every sign-out in the App logged the same generic line, whatever triggered it. When a user reported an unexpected sign-out, the logs could not tell a deliberate sign-out from a reauthentication network error, a SAML requirement, a revoked device, a deleted account, or an OldDot link signing the previous user out. That made sign-out reports hard to investigate.
Solution
clearStorageAndRedirect in src/libs/actions/SignInRedirect.ts now logs the signOutReason it received, so every sign-out path records why it happened. The two transition paths, AuthScreensInitHandler and LogOutPreviousUserPage, log an extra line that also says whether the link named a copilot account, whether the current session was a copilot session, and whether the transition was a support session.
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.94-0 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-10-05. 🎊
The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]
[Contributor] The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to the comment on the PR: NA
Link to the comment on the Issue: NA
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Activity
mountiny commentedon Sep 24, 2026
@parasharrajat I think this did not require C+ and no recordings were made, I assume the reward should be smaller
parasharrajat commentedon Sep 24, 2026
Yes it will be half.
[-]Log the reason for every sign-out[/-][+][Due for payment 2026-10-05] Log the reason for every sign-out[/+]melvin-bot commentedon Sep 28, 2026
@parasharrajat
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.94-0 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-10-05. 🎊
The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]
1 remaining item
parasharrajat commentedon Oct 4, 2026
BugZero Checklist:
[Contributor] The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to the comment on the PR: NA
Link to the comment on the Issue: NA
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue: https://github.com/Expensify/Expensify/issues/689467
Regression Test Proposal
Internal change, not needed.
Do we agree 👍 or 👎
Zapier Logs
Run ID: 00040eee-b119-a5a3-64ad-039a1b14d244melvin-bot commentedon Oct 4, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)melvin-bot commentedon Oct 4, 2026
Payment Summary
Resolving PRs:
[NoQA] Log the reason for every sign-out #101882
Reviewer: @parasharrajat owed $175 via NewDot
Contributor: @adhorodyski does not require payment (Contractor)
BugZero Checklist (@mallenexpensify)
mallenexpensify commentedon Oct 6, 2026
Payment Summary
Contributor+: @parasharrajat due $100 via NewDot
Tests weren't needed on Reviewers Checklist on PR