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
Uber - Invite/Resend buttons unresponsive on Manage invites tab #82601
Version Number: v9.3.20-2 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from BrowserStack:https://test-management.browserstack.com/projects/2219752/folder/27016468/test-cases/64369343 Email or phone of affected tester (no customers): new public account Issue reported by: Applause Internal Team Bug source: Regression TC Execution Device used: MacOS Monterey 12.7.4 / Chrome App Component: Other
Action Performed:
Precondition: sign up new account on public domain (do not use gmail.com. I use applausemail.com). Create workspace with a couple members. Connect to Uber.
Go to ws > Receipt partners
Click on Manage invites
Click on Resend (or Invite) button
Expected Result:
Button clicked. Green tick appears on Resend button (like in production)
👋 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.
Classification: Frontend bug Causing PR: #81779 - "Fix disabled Next button not announced as disabled by screen readers" by @kirillbilchenko (High confidence) Related Issues: None
Recommendation: REVERT
The PR modifies GenericPressable to set fullDisabled={!!props.fullDisabled || !!props.disabled} on web. This change causes the Invite/Resend buttons (which use PressableWithDelayToggle component) to become unresponsive.
Labels: No label changes needed - keeping DeployBlockerCash as this is a frontend bug blocking the App deploy.
Detailed Analysis
Evidence
Issue reproducible in staging (v9.3.20-2) but NOT in production
This causes the Pressable disabled prop to be set to true when either fullDisabled or disabled props are truthy. The PressableWithDelayToggle component has internal logic with accessible={false} and tabIndex={-1} on a nested PressableWithoutFeedback (line 141-154), which may be interacting poorly with the new fullDisabled logic, making the buttons completely unresponsive.
The issue appears to be that the new fullDisabled behavior is too aggressive and prevents click events from firing on components that have certain accessibility configurations.
📣 @kirillbilchenko! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:
Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
Format:
Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>
Activity
melvin-bot commentedon Feb 16, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @brunovjk (
External)melvin-bot commentedon Feb 16, 2026
Triggered auto assignment to @laurenreidexpensify (
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 commentedon Feb 16, 2026
Triggered auto assignment to @AndrewGable (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Feb 16, 2026
Unable to auto-create job on Upwork. The BZ team member should create it manually for this issue.
melvin-bot commentedon Feb 16, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Feb 16, 2026
👋 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:
OSBotify commentedon Feb 16, 2026
Investigation Summary
Classification: Frontend bug
Causing PR: #81779 - "Fix disabled Next button not announced as disabled by screen readers" by @kirillbilchenko (High confidence)
Related Issues: None
Recommendation: REVERT
The PR modifies GenericPressable to set
fullDisabled={!!props.fullDisabled || !!props.disabled}on web. This change causes the Invite/Resend buttons (which use PressableWithDelayToggle component) to become unresponsive.Labels: No label changes needed - keeping
DeployBlockerCashas this is a frontend bug blocking the App deploy.Detailed Analysis
Evidence
Verification
/home/runner/_work/App/App/src/pages/workspace/receiptPartners/EditInviteReceiptPartnerPolicyPage.tsxPressableWithDelayTogglecomponentPressableWithDelayToggleinternally usesPressableWithoutFeedbackwhich extendsGenericPressableRoot Cause
PR #81779 changed
src/components/Pressable/GenericPressable/implementation/index.tsx(web implementation) to automatically set:This causes the Pressable
disabledprop to be set totruewhen eitherfullDisabledordisabledprops are truthy. ThePressableWithDelayTogglecomponent has internal logic withaccessible={false}andtabIndex={-1}on a nested PressableWithoutFeedback (line 141-154), which may be interacting poorly with the newfullDisabledlogic, making the buttons completely unresponsive.The issue appears to be that the new
fullDisabledbehavior is too aggressive and prevents click events from firing on components that have certain accessibility configurations.AndrewGable commentedon Feb 16, 2026
Going to start with the revert suggested above.
kirillbilchenko commentedon Feb 16, 2026
@AndrewGable I don't get why I was tagged by bot? asking because it's not my pr
melvin-bot commentedon Feb 16, 2026
📣 @kirillbilchenko! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:
Format:
AndrewGable commentedon Feb 16, 2026
Just AI hallucination, sorry
m-natarajan commentedon Feb 17, 2026
Not Repro on Windows 10/Chrome/Build v9.3.20-2 PR:82602
2026-02-17.07-08-14.mp4
mountiny commentedon Feb 17, 2026
CPing the revert
m-natarajan commentedon Feb 17, 2026
Not Repro, Windows 10 / Chrome, v9.3.20-4
Repro.-.issue.82601.mp4
AndrewGable commentedon Feb 17, 2026
Thanks @mountiny