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-12-08] SAML-"Require SAML login" toggle is not greyed out when toggling it in offline mode #76243
Version Number: v9.2.65-0 Reproducible in staging?: Yes Reproducible in production?: N/A - new feature, doesn't exist in prod If this was caught during regression testing, add the test name, ID and link from BrowserStack:#74973 Email or phone of affected tester (no customers):applausetester+agadmin@applause.expensifail.com Issue reported by: Applause Internal Team Device used: Windows 11/ Chrome, Samsung S23FE/ Chrome, iPhone 13 Mini/ iOS 26.1 App Component: Other
👋 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 [-]SAML-"Require SAML login" toggle is not greyed out when toggling it in offline mode[/-][+][Due for payment 2025-12-08] SAML-"Require SAML login" toggle is not greyed out when toggling it in offline mode[/+]on Dec 1, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.66-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@lakchote@JmillsExpensify@mhawryluk 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 Nov 27, 2025
Triggered auto assignment to @JmillsExpensify (
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.github-actions commentedon Nov 27, 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 Nov 27, 2025
Triggered auto assignment to @lakchote (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Nov 27, 2025
💬 A slack conversation has been started in #expensify-open-source
lakchote commentedon Nov 27, 2025
@mhawryluk will take a look at the issue. I don't think this should be a blocker given this is offline, and a minor bug.
m-natarajan commentedon Nov 27, 2025
Not repro MacOS Monterey / Chrome Web v9.2.65-4
Screen.Recording.2025-11-27.at.22.47.02.1.mp4
mountiny commentedon Nov 28, 2025
Fixed
[-]SAML-"Require SAML login" toggle is not greyed out when toggling it in offline mode[/-][+][Due for payment 2025-12-08] SAML-"Require SAML login" toggle is not greyed out when toggling it in offline mode[/+]melvin-bot commentedon Dec 1, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.66-3 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-12-08. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Dec 1, 2025
@lakchote @JmillsExpensify @mhawryluk 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]
JmillsExpensify commentedon Dec 3, 2025
Payment summary: $250 @ZhenjaHorbach for PR review and testing. Related do we have a regression test already created for this case?