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 2025-09-04] Android - User signed out of app when updating to '9.1.89-7' #67949
changed the title [-]User signed out of app when updating to '9.1.89-7'[/-][+]Android - User signed out of app when updating to '9.1.89-7'[/+]on Aug 5, 2025
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
Identify the pull request that introduced this issue and revert it.
changed the title [-]Android - User signed out of app when updating to '9.1.89-7'[/-][+][Due for payment 2025-09-04] Android - User signed out of app when updating to '9.1.89-7'[/+]on Aug 28, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.99-11 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@Julesssss@mateuuszzzzz The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero 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]
Activity
melvin-bot commentedon Aug 5, 2025
Triggered auto assignment to @kadiealexander (
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.[-]User[/-][+]User signed out of app when updating to '9.1.89-7'[/+][-]User signed out of app when updating to '9.1.89-7'[/-][+]Android - User signed out of app when updating to '9.1.89-7'[/+]melvin-bot commentedon Aug 5, 2025
Triggered auto assignment to @MarioExpensify (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Aug 5, 2025
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
melvin-bot commentedon Aug 5, 2025
💬 A slack conversation has been started in #expensify-open-source
49 remaining items
Julesssss commentedon Aug 26, 2025
Reopening for QA verification
Julesssss commentedon Aug 26, 2025
Was verified resolved during this pre-merge round of QA testing. PR has been merged, now awaiting deployment.
Julesssss commentedon Aug 26, 2025
Lets give it a few days for the changes to be thoroughly tested on staging and be deployed to prod before we close this one out.
melvin-bot commentedon Aug 27, 2025
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
[-]Android - User signed out of app when updating to '9.1.89-7'[/-][+][Due for payment 2025-09-04] Android - User signed out of app when updating to '9.1.89-7'[/+]melvin-bot commentedon Aug 28, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Aug 28, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.99-11 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 2025-09-04. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Aug 28, 2025
@Julesssss @mateuuszzzzz The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero 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]
Julesssss commentedon Aug 28, 2025
Issue hit prod, closing