Android - Account setting - Missing Expensify code and Request Tax exempt status

[applause-bot]

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.

---

Version Number: v9.4.55-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: https://test-management.browserstack.com/projects/2219752/folder/52723381/test-cases/41236708
Email or phone of affected tester (no customers): lattelover1412+180810@gmail.com
Issue reported by: Applause Internal Team
Bug source: Regression TC Execution
Device used: android
App Component: User Settings

Action Performed:

1. Open the link www.staging.new.expensify.com
2. Create a new user and select any option OTHER than "Manage my team expense" (in my case, I selected "Track expense for my business") >> Follow the onboarding flow
3. Verify new Workspace is created
4. Navigate to Account >> Subscription >> Edit subscription

Expected Result:

There should be "Expensify code" and "Request tax exempt status" displayed

Actual Result:

Step 12, the requirement is required to Verify "Expensify code" and "Request tax exempt status" are displayed. However, there are no "Expensify code" and "Request tax exempt status" displayed

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome Safari

Screenshots/Videos

Bug7236094_1787037746225.23.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7236094

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022089620752345019332
• Upwork Job ID: 2089620752345019332
• Last Price Increase: 2026-08-18

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/eb4007322ea682ea6a3b556c62e33ef400b0f7c3a28a4923f0a33e7dc2ef144e

https://platform.applause.com/services/links/v1/external/caba4d44a2822cda1c78c6a52062780b011b235418ba76cc92a621f2bef72305

https://platform.applause.com/services/links/v1/external/6d6f19e138b3f46b4d294a496f329cb48c99bf3c9801d4a24b45364d80de28bf

[MelvinBot]

Issue Analysis

Root cause: This is working as designed on mobile, not a code regression. The Android/iOS app intentionally renders a read-only subscription page that omits all editable subscription controls — including "Expensify code" and "Request tax exempt status." These two rows have never existed in the native page; they only exist in the web version. The onboarding choice in the repro steps is a red herring — the rows are absent on mobile regardless of which plan the workspace ends up on.

• Native SubscriptionSettings/index.native.tsx:108 renders the banner "You can't make changes to your subscription in the mobile app" (mobileReducedFunctionalityMessage) and shows only pricing/plan + subscription-size info — no editable rows at all.
• Web SubscriptionSettings/index.tsx:328-362 renders both the Expensify code and Request tax exempt rows unconditionally.

Recommendation: This looks like a stale test-case expectation rather than an app bug — TC 41236708 step 12 expects web-only rows on a platform whose subscription page is deliberately reduced-functionality. BugZero/product should decide between:

1. Update the regression TC to reflect that mobile is intentionally read-only (most likely correct), or
2. Treat as a feature request to bring these controls to mobile — in which case the fix is to port the two MenuItemWithTopDescription rows from the web file into the native file.

Investigation details

• The native index.native.tsx has 42 commits back to 2024-06; zero occurrences of expensifyCode / requestTaxExempt / privatePromoCode at any point (checked at 4d7d132f, 934fc22d, 1ef4eba2, and current HEAD). They were never removed — they were never added.
• On web, the tax-exempt row has existed since the 2025-03 mobile RHP move; the Expensify code row was added by feat: Add Expensify code feature in Subscription settings #79829 (merged 2026-02-16) and expanded by feat: enable Expensify Card for Collect workspaces and update subscription settings UI for Collect #83455 (2026-03-20) / Always show expensify code field and hide code only if secretPromoCode #90151 (2026-05-20). None of these added the rows to the native file.
• Notably feat: enable Expensify Card for Collect workspaces and update subscription settings UI for Collect #83455 edited both the web and native files in the same PR yet still added no editable rows to native — reinforcing that the native page is deliberately kept read-only.
• I did not run a device test: the report is Android/iOS App only, and this run can only drive web (where the rows render correctly), so a web test cannot reproduce a native-only, works-as-designed behavior. The conclusion rests on the code + history evidence above (high confidence).

---

Next Steps for Contributor+ team:
To accept a mobile parity change: @MelvinBot implement [this](https://github.com/Expensify/App/blob/eb861f7268be2cc2dc1d3b279685a1e0a7707a18/src/pages/settings/Subscription/SubscriptionSettings/index.native.tsx#L108) to create a draft PR porting the two rows to native.
To refine: @MelvinBot <your feedback>
To reject: If mobile should stay read-only, close as working-as-designed and update the regression TC.

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @rojiphil (External)

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~022089620752345019332

[dilshodmackbook-sketch]

@rojiphil before this gets closed as working-as-designed based on the automated analysis above, I think the Melvin analysis is half right and half wrong, and the wrong half is the one that matters here.

Melvin lumped both rows together and concluded the whole native page is deliberately read-only, using the mobileReducedFunctionalityMessage banner as the evidence. But that banner is specifically about not being able to change your subscription plan/size on mobile. "Request tax exempt status" is not a subscription change at all — requestTaxExempt() just fires API.write(WRITE_COMMANDS.REQUEST_TAX_EXEMPTION, null) and opens Concierge (Subscription.ts#L430). It is an account-level request whose handler is already fully cross-platform, so the reduced-functionality banner never covered it. Its absence on native is a porting gap, not a design decision.

The "these rows were never added, therefore it's intentional" reasoning is also an inference error — never-added proves omission, not intent, especially when the handler works on mobile as-is. And Melvin itself flagged it never ran a device test, so the WAD conclusion on the native-only half rests entirely on git history.

Where Melvin is right: the Expensify code row should stay off native, but not for the "read-only page" reason it gave — it's because that row's destination page is intentionally a Not Found stub on native (ExpensifyCodePage/index.native.tsx, shipped that way in #96910). Porting it would just lead to a 404. So the two rows actually have different answers, which the analysis missed by treating them as one.

Net: this is a real bug for the tax exempt row (port it to index.native.tsx, reusing the same requestTaxExempt + navigateToConciergeChat the web row already uses), and genuinely out of scope for the Expensify code row. Updating the regression TC to drop only the Expensify code expectation would also be consistent with that.

If you'd like, I'm happy to write up a full proposal with the exact change and a render test — just let me know.

[melvin-bot]

@rojiphil Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[melvin-bot]

@rojiphil 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

[melvin-bot]

@rojiphil Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it!

[rojiphil]

This is working as designed on mobile, not a code regression. The Android/iOS app intentionally renders a read-only subscription page that omits all editable subscription controls — including "Expensify code" and "Request tax exempt status." These two rows have never existed in the native page; they only exist in the web version.

@Expensify/product This issue is raised as part of the regression test case execution. However, the referred regression test case does not explicitly expect the Expensify code and Request tax exempt status to be displayed in native apps. Melvin's analysis is also on similar lines as mentioned above. Is the expected result in this issue intentional?

98848-web-reproduction_001.mp4