Skip to content

fix: [Accessibility][Tracking] Restructure Accessibility Grouping#80442

Merged
madmax330 merged 21 commits intoExpensify:mainfrom
TaduJR:fix-Accessibility-Tracking-Restructure-Accessibility-Grouping
Mar 9, 2026
Merged

fix: [Accessibility][Tracking] Restructure Accessibility Grouping#80442
madmax330 merged 21 commits intoExpensify:mainfrom
TaduJR:fix-Accessibility-Tracking-Restructure-Accessibility-Grouping

Conversation

@TaduJR
Copy link
Contributor

@TaduJR TaduJR commented Jan 25, 2026

Explanation of Change

This PR fixes multiple accessibility grouping issues where iOS VoiceOver absorbed interactive child elements (buttons) into their parent containers, making them unfocusable and unactivatable.

Fixes

  1. ReferralProgramCTA (#76902): The close button was nested inside a PressableWithoutFeedback, making it invisible to VoiceOver. Restructured so the outer element is a plain View with navigate and close as sibling pressables.

  2. ExpenseReportListItem/Row (#77538): On mobile, the entire expense report row was grouped as one accessibility element, hiding the ActionCell button (e.g., "View", "Approve"). Added accessible={false} to BaseListItem and created an inner accessible group with a computed label including user name, report title, subtitle, status, and amount.

  3. UserListItem (#77467 — Start Chat): The "Add to group" button was absorbed into the contact row. Added an inner View with accessible and role=button for the contact info, making the "Add to group" button independently focusable. The rightHandSideComponent function is evaluated to check actual render output, so rows without a visible button (e.g., Expensify emails, self-DMs) keep default grouping.

  4. ExpensifyCardPage (#77467 — Expensify Card): "Reveal details" and "Reveal CVV" buttons were absorbed into the card number container. Added shouldBeAccessible={false} to the two MenuItemWithTopDescription instances.

  5. BaseListItem: New accessible prop forwarded to PressableWithFeedback. When accessible={false}, the accessibilityLabel is cleared to prevent duplicate labels in the accessibility tree.

Fixed Issues

$ #79238
PROPOSAL: #79238 (comment)

Tests

Issue #76902 — ReferralProgramCTA buttons grouped

  1. Sign in and navigate to + > Track distance
  2. Select start/stop points, tap Next, and select a workspace (e.g., "Expensify.org / Teachers Unite")
  3. Observe the referral banner ("Submit an expense, refer your boss") with its close (X) button
  4. iOS VoiceOver: Swipe right through the banner — verify "refer your boss" and the close (X) button are announced as two separate buttons, each independently focusable and activatable
  5. Web (JAWS/NVDA): Tab through the banner — verify each button receives focus separately with correct role announcements

Issue #77538 — Expense report record details and buttons grouped

  1. Sign in on iOS with VoiceOver enabled
  2. Navigate to the Reports tab at the bottom of the screen
  3. Swipe right to focus on expense report tiles
  4. Verify that the report details (name, status, amount) and the action button (e.g., "View") are announced as separate focusable elements, not grouped into one
  5. Verify the report details group announces: user name, report title, subtitle (e.g., "From X's expenses in Y's Workspace"), status, and amount
  6. Verify double-tapping the report details group still opens/selects the report

Issue #77467 — Occurrence 1: Start Chat "Add to group" button

  1. Sign in on iOS with VoiceOver enabled
  2. Tap the + icon and select Start chat
  3. Type a contact name in the search field (e.g., "Concierge")
  4. Swipe right through the contact row
  5. Verify the contact info (name, email) and the "Add to group" button are announced as two separate focusable elements
  6. Verify double-tapping the contact info group still selects the contact
  7. Verify double-tapping the "Add to group" button adds the contact to the group
  8. Verify Expensify system emails (e.g., accounting@expensify.com) show as a single grouped element with no "Add to group" button

Issue #77467 — Occurrence 2: Expensify Card "Reveal details" button

  1. Sign in on iOS with VoiceOver enabled (account must have an Expensify Card)
  2. Navigate to Account > Wallet > Expensify Card
  3. Swipe right to focus on the Virtual card number row
  4. Verify the card number details and the "Reveal details" button are announced as separate focusable elements
  5. Verify double-tapping "Reveal details" reveals the full card number
  6. If a travel card with CVV is present, verify the "Reveal CVV" button is also independently focusable
  • Verify that no errors appear in the JS console

Offline tests

Same as tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."
Same as tests

  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
    • MacOS: Desktop
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I verified there are no new alerts related to the canBeMissing param for useOnyx
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
Screen_Recording_20260302_141316_New.Expensify.Dev.mp4
Android: mWeb Chrome
Android-mWeb.mp4
iOS: Native
iOS-Native.mp4
iOS: mWeb Safari
MacOS: Chrome / Safari
Mac-Chrome.mp4

@TaduJR TaduJR requested review from a team as code owners January 25, 2026 10:01
@melvin-bot melvin-bot bot requested a review from heyjennahay January 25, 2026 10:01
@melvin-bot
Copy link

melvin-bot bot commented Jan 25, 2026

Hey! I see that you made changes to our Form component. Make sure to update the docs in FORMS.md accordingly. Cheers!

@melvin-bot melvin-bot bot requested review from eVoloshchak and removed request for a team January 25, 2026 10:01
@melvin-bot
Copy link

melvin-bot bot commented Jan 25, 2026

@eVoloshchak Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c74c4a1781

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

@TaduJR TaduJR marked this pull request as draft January 25, 2026 13:12
@TaduJR TaduJR force-pushed the fix-Accessibility-Tracking-Restructure-Accessibility-Grouping branch from 4433d3d to 6282eb9 Compare February 4, 2026 07:17
@codecov
Copy link

codecov bot commented Feb 4, 2026

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines Coverage Δ
src/CONST/index.ts 94.30% <ø> (ø)
src/components/ReferralProgramCTA.tsx 100.00% <100.00%> (ø)
...ponents/SelectionListWithSections/BaseListItem.tsx 95.65% <100.00%> (+0.09%) ⬆️
...nListWithSections/Search/ExpenseReportListItem.tsx 0.00% <ø> (ø)
...ponents/SelectionListWithSections/UserListItem.tsx 80.39% <100.00%> (+3.11%) ⬆️
.../pages/settings/Wallet/ExpensifyCardPage/index.tsx 65.21% <50.00%> (-0.27%) ⬇️
...stWithSections/Search/ExpenseReportListItemRow.tsx 0.00% <0.00%> (ø)
... and 12 files with indirect coverage changes

…referral CTA

  - Restructure ExpenseReportListItemRow mobile view so VoiceOver reads report
    details as a group and Submit button as independently focusable (Expensify#77538)
  - Fix nested buttons in ReferralProgramCTA by converting to sibling structure (Expensify#76902)
  - Add accessible prop to BaseListItem for opt-in VoiceOver grouping control
@TaduJR TaduJR force-pushed the fix-Accessibility-Tracking-Restructure-Accessibility-Grouping branch from 6282eb9 to a57934e Compare February 21, 2026 17:56
@TaduJR TaduJR marked this pull request as ready for review February 22, 2026 06:28
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 003842ddb3

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

@eVoloshchak
Copy link
Contributor

@TaduJR, iOS: mWeb Safari and Android screen recordings are missing, let's double-check nothing has been broken on these platforms

@rushatgabhane
Copy link
Member

@MelvinBot merge main and resolve conflicts

…Grouping

Resolved conflict in ReferralProgramCTA.tsx:
- Kept the PR's View wrapper structure (accessibility fix) with separate
  pressable children for navigate and close actions
- Adopted main's updated sentry labels (REFERRAL_PROGRAM.CTA and
  REFERRAL_PROGRAM.DISMISS_BUTTON) replacing the PR's REFERRAL_CTA labels
- Adopted main's lazy icon loading (useMemoizedLazyExpensifyIcons)
- Removed the now-redundant REFERRAL_CTA sentry label constant from CONST

Co-authored-by: Rushat Gabhane <rushatgabhane@users.noreply.github.com>
@MelvinBot
Copy link
Contributor

Merged main into this branch and resolved the conflict in src/components/ReferralProgramCTA.tsx.

Conflict resolution details:

  • Kept the PR's View wrapper structure (the core accessibility fix) with separate pressable children for the navigate and close actions
  • Adopted main's updated sentry labels (REFERRAL_PROGRAM.CTA and REFERRAL_PROGRAM.DISMISS_BUTTON) replacing the PR's REFERRAL_CTA labels
  • Adopted main's lazy icon loading (useMemoizedLazyExpensifyIcons)
  • Removed the now-redundant REFERRAL_CTA sentry label constant from CONST/index.ts
  • Fixed a duplicate sentryLabel prop on the close button that resulted from the auto-merge

@eVoloshchak
Copy link
Contributor

eVoloshchak commented Mar 2, 2026

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified proper code patterns were followed (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp
Screen.Recording.2026-03-09.at.09.34.02.mov
Screen.Recording.2026-03-09.at.09.31.40.mov
Android: mWeb Chrome
Screen.Recording.2026-03-09.at.09.36.46.mov
Screen.Recording.2026-03-09.at.09.34.37.mov
iOS: HybridApp
Screen.Recording.2026-03-09.at.09.24.52.mov
Screen.Recording.2026-03-09.at.09.17.36.mov
iOS: mWeb Safari
Screen.Recording.2026-03-09.at.09.28.33.mov
Screen.Recording.2026-03-09.at.09.26.05.mov
MacOS: Chrome / Safari
Screen.Recording.2026-03-09.at.09.05.40.mov
Screen.Recording.2026-03-02.at.14.09.52.mov
Screen.Recording.2026-03-09.at.09.07.57.mov

@eVoloshchak
Copy link
Contributor

eVoloshchak commented Mar 2, 2026

Issue #77538 — Expense report record details and buttons grouped

  1. Navigate to the Reports tab at the bottom of the screen
  2. Verify that the report details (name, status, amount) and the action button (e.g., "View") are announced as separate focusable elements, not grouped into one

This doesn't work on Web, name, status, and amount are not focused separately

Screen.Recording.2026-03-02.at.14.34.33.mov

On IOS this works for Reports, but not for Expenses and other tabs. Is this expected?

Screen.Recording.2026-03-02.at.14.37.20.mov

The same bug is reproducible on iOS: mWeb Safari (iOS: mWeb Safari screen recording is missing)

@eVoloshchak
Copy link
Contributor

eVoloshchak commented Mar 2, 2026

Issue #76902 — ReferralProgramCTA buttons grouped

On iOS native, "Submit an expense, refer your boss" is not vertically aligned

Before:
Simulator Screenshot - iPhone 15 Pro - 2026-03-02 at 14 49 19

After:

Simulator Screenshot - iPhone 15 Pro - 2026-03-02 at 14 46 45

@TaduJR
Copy link
Contributor Author

TaduJR commented Mar 2, 2026

This doesn't work on Web, name, status, and amount are not focused separately

This is expected for Web Per W3 guideline, non-interactive elements should be focusable with Ctrl + Option + Arrow Key

On IOS this works for Reports, but not for Expenses and other tabs. Is this expected?

Once the 'Reports' screen opens, swipe right to focus on the record tiles or details that are available on the screen.

The issue description from #77538 says the above, it only scopes to Reports, should we do the same for Expenses too?

On iOS native, "Submit an expense, refer your boss" is not vertically aligned

Taking a look

@TaduJR
Copy link
Contributor Author

TaduJR commented Mar 2, 2026

The issue description from #77538 says the above, it only scopes to Reports, should we do the same for Expenses too?

cc @rushatgabhane on this one

Thanks!

@TaduJR
Copy link
Contributor Author

TaduJR commented Mar 4, 2026

On iOS native, "Submit an expense, refer your boss" is not vertically aligned

Fixed on latest commit.

…bility-Tracking-Restructure-Accessibility-Grouping

# Conflicts:
#	src/components/SelectionListWithSections/Search/ExpenseReportListItemRow.tsx
@eVoloshchak
Copy link
Contributor

@rushatgabhane, could you weigh in on #80442 (comment) please?

@TaduJR
Copy link
Contributor Author

TaduJR commented Mar 4, 2026

@rushatgabhane, could you weigh in on #80442 (comment) please?

Hey @eVoloshchak

Sorry I thought I notified here.

We discussed with @rushatgabhane and decided to handle the remains or Expense etc.. on follow up PR.

Copy link
Contributor

@eVoloshchak eVoloshchak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@melvin-bot melvin-bot bot requested a review from madmax330 March 9, 2026 08:39
@eVoloshchak
Copy link
Contributor

eVoloshchak commented Mar 9, 2026

@MelvinBot, merge main, resolve the conflicts, and push the changes to this branch

@MelvinBot
Copy link
Contributor

I'd be happy to help merge main and resolve conflicts, but I can't push code changes to this PR because I didn't open it and I'm not listed as an assignee.

To have me do this, please add me as an assignee on the PR and then retry your request.

…bility-Tracking-Restructure-Accessibility-Grouping

# Conflicts:
#	src/components/SelectionListWithSections/UserListItem.tsx
@rushatgabhane
Copy link
Member

@madmax330 all yours!

@madmax330 madmax330 merged commit 9044336 into Expensify:main Mar 9, 2026
29 checks passed
@OSBotify
Copy link
Contributor

OSBotify commented Mar 9, 2026

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@github-actions
Copy link
Contributor

github-actions bot commented Mar 9, 2026

🚧 @madmax330 has triggered a test Expensify/App build. You can view the workflow run here.

@OSBotify
Copy link
Contributor

OSBotify commented Mar 9, 2026

🚀 Deployed to staging by https://github.com/madmax330 in version: 9.3.34-0 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/luacmartins in version: 9.3.34-2 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

@rushatgabhane
Copy link
Member

Lessgooo!

@TaduJR
Copy link
Contributor Author

TaduJR commented Mar 11, 2026

Wohooo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants