Skip to content

[Due for payment 2026-10-15] Home-Changing font size to maximum not showing insights in footer #102787

Closed

Description

@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.5.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: #101218
Email or phone of affected tester (no customers): dreamnitethedragon+vegst@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Redmi note 10s android 13
App Component: Chat Report View

Action Performed:

  1. Launch app
  2. Go to beta override and enable InsightsPage
  3. Note navigation icons shows insights in footer
  4. Change device font size to maximum
  5. Close and reopen the app
  6. Note insights icon is missing in footer
  7. Go to betaride and note insightspage is enabled
  8. Change font size to small
  9. Close and reopen the app
  10. Note betaride shows insightspage is enabled but Insights icon is not shown in footer
  11. Via four finger gesture, disable and enable InsightsPage
  12. Note now insights is shown in footer

Expected Result:

Changing font size to maximum must show insights in footer as it is enabled in betaride option.

Actual Result:

Changing font size to maximum not showing insights in footer although it is enabled in betaride option.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7274548_1790869440011.Screenrecorder-2026-10-01-21-04-09-456.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Svetlana Lazutkina
Bug ID: 7274548

Issue OwnerCurrent Issue Owner: @mallenexpensify

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Oct 1, 2026
  2. applause-bot commented on Oct 1, 2026

    @applause-bot
    Author

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

  3. melvin-bot commented on Oct 1, 2026

    @melvin-bot

    @luacmartins recently merged #101218, but they are OOO right now, so I'll auto-assign someone else.

  4. github-actions commented on Oct 1, 2026

    @github-actions
    Contributor

    👋 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:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  5. melvin-bot commented on Oct 1, 2026

    @melvin-bot

    Triggered auto assignment to @amyevans (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  6. melvin-bot commented on Oct 1, 2026

    @melvin-bot

    @luacmartins @cristipaval @truph01 you have been assigned to this deploy blocker because you reviewed the offending PR: #101218

  7. 23 remaining items

  8. melvin-bot commented on Oct 13, 2026

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  9. truph01 commented on Oct 14, 2026

    @truph01
    Contributor

    Contributor+ Checklist:

    • [Contributor] The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

      Link to the comment on the PR: Add beta override switches to the Test Tool menu #99444 (comment)
      Link to the comment on the Issue:

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

      Link to discussion:

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

    Regression Test Proposal

    Precondition:

    Test:

    Which builds can show this. The symptom only exists on a build compiled as production whose resolved environment is staging — an Android staging APK installed outside the Play Store, or an iOS TestFlight build. That combination is what makes CONFIG.ENVIRONMENT report production while the native beta check later reports staging. A debug build sets ENVIRONMENT=development and an ad-hoc build sets adhoc, and getEnvironment short-circuits on both before it reaches the beta checker, so neither ever enters the state where the bug exists — before or after this change.

    Tested on a debug build and it behaves as expected: overrides apply immediately and clear correctly. That is the expected result either way, since the production gate is never engaged there.

    Why there are no screenshots or a video. No build available to us reaches the state where the bug exists. Producing one would mean hand-building a signed productionRelease and installing it outside the Play Store. Steps 1–3 are the actual regression and need a staging build — we'd be grateful if someone with staging access could run them.

    1. On an Android staging build installed outside the Play Store, open Troubleshoot > Beta overrides and switch on a beta your account does not have — InsightsPage adds a visible tab.
    2. Verify the Insights tab appears in the footer.
    3. Force-stop the app and reopen it. Verify the tab is still there, without touching the override. Before this change it was missing while the overrides page still showed the beta as enabled.
    4. On any non-production build, toggle a beta on and verify the feature it gates appears immediately.
    5. Toggle the same beta off and verify the account value is restored and the "Overridden" badge clears.
    6. On a production build, verify Troubleshoot shows no Beta overrides row and that opening /beta-overrides by deep link shows the not-found page.

    Do we agree 👍 or 👎

  10. melvin-bot commented on Oct 14, 2026

    @melvin-bot

    Payment Summary

    Resolving PRs:

    BugZero Checklist (@mallenexpensify)

    • I have confirmed assignees, roles, and Upwork contracts look correct
    • I have paid out Upwork contracts / manual NewDot requests
    • [BugZero Assignee] I have created a GH issue for creating/updating the regression test once above steps have been agreed upon
  11. melvin-bot commented on Oct 16, 2026

    @melvin-bot

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

  12. mallenexpensify commented on Oct 17, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor+: @truph01 due $175 via NewDot

    @truph01 please completely fill out the C+ checklist

    [Contributor] The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

    Link to the comment on the PR:
    Link to the comment on the Issue:

  13. truph01 commented on Oct 17, 2026

    @truph01
    Contributor

    @MelvinBot Based on #102787 (comment) please comment on the exact line in #99444 that causes this bug.

  14. MelvinBot commented on Oct 17, 2026

    @MelvinBot
    Contributor

    truph01 I commented on the line that causes this bug: src/libs/Permissions.ts:16 in Add beta override switches to the Test Tool menu.

    The line is isProductionEnvironment = value;. It fixes the environment flag after startup, but in a plain module variable that React can't see. usePermissions never recomputes, so the tab bar keeps ignoring the override after a cold start. Re-resolve beta overrides once the environment settles fixed this.

    You can use that link for "Link to the comment on the PR" in your checklist.


    view run

  15. truph01 commented on Oct 17, 2026

    @truph01
    Contributor

    @truph01 please completely fill out the C+ checklist

    @mallenexpensify I filled out the C+ checklist

  16. garrettmknight commented on Oct 19, 2026

    @garrettmknight
    Contributor

    $175 approved for @truph01

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

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions