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-19] [SAML Configuration] "Invalid character" error when saving default Identity Provider MetaData #76376
Version Number: 9.2.66-0 Reproducible in staging?: Yes Reproducible in production?: Yes 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@applause.expensifail.com Issue reported by: Applause Internal Team Device used: Mac 26.1 / Chrome App Component: Other
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.77-1 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@NikkiWines / @mountiny@brianlee-expensify@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 Dec 1, 2025
Triggered auto assignment to @brianlee-expensify (
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.[-]SAML Settings - "Invalid character" error when saving default Identity Provider MetaData[/-][+][SAML Configuration] "Invalid character" error when saving default Identity Provider MetaData[/+][-][SAML Configuration] "Invalid character" error when saving default Identity Provider MetaData[/-][+][Due for payment 2025-12-19] [SAML Configuration] "Invalid character" error when saving default Identity Provider MetaData[/+]melvin-bot commentedon Dec 12, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Dec 12, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.77-1 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-19. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Dec 12, 2025
@NikkiWines / @mountiny @brianlee-expensify @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]
mountiny commentedon Dec 14, 2025
I believe we can close as project payment and testing will cover this