[Home Page] Remove Beta Gate for Release 1 #80965

WojtekBoman · 2026-01-30T00:22:44Z

Explanation of Change

This PR fixes a padding issue in the Home Page AnnouncementSection and DiscoverSection components and adds styling improvements for both sections.

Changes made:

Fixed padding issue: Changed from pl5/pl8 (padding-left only) to ph5/ph8 (padding-horizontal) in both AnnouncementSection and DiscoverSection to ensure proper symmetric padding on both sides of the content.
Added compact view mode: Applied viewMode={CONST.OPTION_MODE.COMPACT} and hasSubMenuItems to both sections for consistent compact styling.
Added rightIconWrapperStyle prop to MenuItem: Introduced a new optional prop to allow custom styling for the right icon wrapper, enabling the sections to apply styles.pl2 spacing for proper alignment of the arrow icon.

Fixed Issues

$ #80139
$ #80873
PROPOSAL:

Tests

Navigate to the Home Page
Verify the Announcements section displays correctly with proper padding on both left and right sides
Verify the Discover section displays correctly with proper padding on both left and right sides
Verify the arrow icons on the right side of each menu item are properly aligned
Resize the window between narrow and wide layouts to confirm padding adjusts appropriately (ph5 for narrow, ph8 for wide)
Tap on an announcement item and verify it opens the correct URL
Verify that no errors appear in the JS console

Offline tests

Enable airplane mode / disconnect from the internet
Navigate to the Home Page
Verify the Announcements section still displays correctly with proper padding
Verify the Discover section still displays correctly with proper padding

QA Steps

Navigate to the Home Page
Verify the Announcements section has proper horizontal padding (not just left padding)
Verify the Discover section has proper horizontal padding (not just left padding)
Verify arrow icons are properly aligned with consistent spacing
Test on both narrow (mobile) and wide (desktop) layouts
Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

codecov · 2026-01-30T00:32:35Z

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	`87.50% <ø> (ø)`
src/ROUTES.ts	`13.03% <ø> (-0.12%)`	⬇️
src/components/FloatingActionButton.tsx	`95.65% <100.00%> (-1.32%)`	⬇️
.../FloatingCameraButton/BaseFloatingCameraButton.tsx	`84.21% <ø> (-0.79%)`	⬇️
src/components/MenuItem.tsx	`87.80% <ø> (ø)`
src/libs/Navigation/AppNavigator/AuthScreens.tsx	`53.12% <ø> (ø)`
src/libs/Navigation/AppNavigator/PublicScreens.tsx	`100.00% <ø> (ø)`
src/libs/Navigation/helpers/getRedirectedPath.ts	`100.00% <100.00%> (ø)`
src/libs/Navigation/helpers/getStateFromPath.ts	`87.50% <100.00%> (+1.78%)`	⬆️
src/pages/home/AnnouncementSection.tsx	`87.50% <100.00%> (+87.50%)`	⬆️
... and 10 more
... and 107 files with indirect coverage changes

github-actions · 2026-01-30T00:37:23Z

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

melvin-bot · 2026-01-30T01:07:07Z

@Ollyws 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]

WojtekBoman · 2026-01-30T01:07:28Z

cc: @ZhenjaHorbach @grgia for review

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 268d095c5a

ℹ️ 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".

chatgpt-codex-connector · 2026-01-30T01:22:49Z

src/ROUTES.ts

    // This route renders the list of reports.
-    INBOX: 'home',
-    // @TODO: Rename it to 'home' and INBOX to 'inbox' when removing the newDotHome beta
-    HOME: 'home-page',
+    INBOX: 'inbox',
+    HOME: 'home',


Keep legacy /home-page route for existing links

This change drops the home-page path entirely by redefining ROUTES.HOME to home with no alias. Any users who had the beta enabled could have /home-page stored as their last visited path (restored on startup via NavigationRoot), and external links or bookmarks can still point to that URL. With no route match, those cases will now land on Not Found or fail to restore the last session. Consider adding a redirect/alias for home-page or migrating stored paths to home to avoid a regression for existing users.

Useful? React with 👍 / 👎.

github-actions · 2026-01-30T02:32:31Z

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

github-actions · 2026-01-30T03:04:55Z

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #80965.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-fe48398c0d98bc3519f53c66aa2c62c2b021eb60/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-8acfea44c8e530d405efc06fdbfce73c29aa85b0/index.html

Web 🕸️
https://80965.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

mountiny · 2026-01-30T03:05:04Z

Asked for the testing

ZhenjaHorbach · 2026-01-30T09:03:02Z

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 there are no new alerts related to the canBeMissing param for useOnyx
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

2026-01-30.12.50.46.mov

Android: mWeb Chrome

2026-01-30.12.46.27.mov

iOS: HybridApp

2026-01-30.12.50.46.mov

iOS: mWeb Safari

2026-01-30.12.46.27.mov

MacOS: Chrome / Safari

2026-01-30.10.21.01.mov

ZhenjaHorbach · 2026-01-30T09:28:35Z

I still can reproduce this issue
#80931 (comment)

The easiest way is with throttling enabled

2026-01-30.10.24.52.mov

jponikarchuk · 2026-01-30T11:15:52Z

Home - "Pay 1 report" is shown after approver leaves workspace

Version Number: v9.3.11-12 PR:80965
Reproducible in staging?: No
Reproducible in production?: No
Email or phone of affected tester (no customers): huisdhbisubhdiushuids2@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 26.1 / Chrome

Action Performed:

Precondition:

Admin invites non-admin approver and member to the workspace.

Go to 80965.pr-testing.expensify.com/
[Member] Go to workspace chat.
[Member] Create an expense. Do not click Submit on the preview.
[Non-admin approver] Open member's workspace chat.
[Non-admin approver] Leave the workspace.
[Non-admin approver] Go to Home.

Expected Result:

"Pay 1 report" will not appear on For you section.

Actual Result:

"Pay 1 report" appears on For you section after approver leaves workspace.

Workaround:

Unknown

Platforms:

Screenshots/Videos

1.mp4

jponikarchuk · 2026-01-30T11:23:17Z

Inbox - Unending skeleton loader when opening inbox

Version Number: v9.3.11-12 PR:80965
Reproducible in staging?: No
Reproducible in production?: No
Email or phone of affected tester (no customers): expensify416+da2@gmail.com
Issue reported by: Applause Internal Team
Device used: macOS chrome

Action Performed:

Go to https://80965.pr-testing.expensify.com/
Enter sign in email > Continue > Join
Click Skip > Track and budget expense > Enter name > Continue > Skip
Click on Inbox
If there is no skeleton repeat step 1 to 4 one more time

Expected Result:

Chat should load

Actual Result:

Unending skeleton loader

Workaround:

Unknown

Platforms:

Screenshots/Videos

1.mp4

mitarachim · 2026-01-30T11:28:01Z

Onboarding - "This content is blocked" page opens when invited member opens onboarding

Version Number: v9.3.11-12 PR:80965
Reproducible in staging?: No
Reproducible in production?: No
Email or phone of affected tester (no customers): yonghongkok2+sdj11noisjndoinjs@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 26.1 / Chrome

Action Performed:

Precondition:

Admin invites a new member (no Expensify account yet) to the workspace.

Go to 80965.pr-testing.expensify.com/
Log in as the invited member.
Open FAB > Take a 2-minute test drive.

Expected Result:

Test drive page opens without issue.

Actual Result:

"This content is blocked" page opens.

Workaround:

Unknown

Platforms:

Screenshots/Videos

Bug7061849_1769771216471.2.mp4

github-actions · 2026-01-30T21:05:30Z

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

github-actions · 2026-01-30T21:28:12Z

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #80965.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-e29d3adfd7cb6e6c3409a010d11108d1060b4d22/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-3329c130117f9e7591d8ea45c586106845c65f65/index.html

Web 🕸️
https://80965.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

adamgrzybowski · 2026-01-30T21:36:54Z

Hey @ZhenjaHorbach, could you please retest this PR? I think we are so close to merging this!

dannymcclain · 2026-01-30T21:55:59Z

Looking good! Mentioned this to Vit in person, but for posterity, I think the only thing we need is the hover state on the to-do rows that Shawn mentioned somewhere at some point.

ZhenjaHorbach · 2026-01-30T22:03:04Z

About this issue
#80965 (comment)
https://swmansion.slack.com/docs/T03Q9AMJJ/F0ABVSK9S9H

Are we going to fix this or is it not ours? 😅

ZhenjaHorbach · 2026-01-30T22:09:02Z

Weird
I can still reproduce this issue

#80965

2026-01-30.23.07.37.mov

m-natarajan · 2026-01-30T22:16:09Z

#80965 (comment)

Not repro, Win 11 chrome, v9.3.11-15 PR:80965

Recording.2323.mp4

#80965 (comment)
Not repro, Win 11 chrome, v9.3.11-15 PR:80965

Recording.2322.mp4

#80965 (comment)
Page is scrollable, Not sure where the truncation is (iPhone Xs)
Fixed

RPReplay_Final1769810493.MP4

ZhenjaHorbach · 2026-01-30T22:16:54Z

@dannymcclain
Do we need to update the image?
Since the elements are cut a bit unevenly 😅

ZhenjaHorbach · 2026-01-30T22:21:21Z

#80965 (comment) Page is scrollable, Not sure where the truncation is (iPhone Xs)

RPReplay_Final1769810493.MP4

I talked about it 😅

But everything's good now!

mountiny · 2026-01-30T22:34:08Z

Looking good! Mentioned this to Vit in person, but for posterity, I think the only thing we need is the hover state on the to-do rows that Shawn mentioned somewhere at some point.

Should be fixed

dannymcclain · 2026-01-30T22:53:12Z

Do we need to update the image? Since the elements are cut a bit unevenly 😅

Yeah if we're using that thumbs up image anywhere let's try replacing it with this one if we can (this is not a blocker though).

simple-illustration__thumbsupstars-home.svg.zip

OSBotify · 2026-01-31T00:20:39Z

🚀 Deployed to staging by https://github.com/mountiny in version: 9.3.11-17 🚀

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

izarutskaya · 2026-02-02T09:32:48Z

Regression Ad-hoc is at 93%

Just 5 IOS slots and 1 Android pending validation.

melvin-bot bot assigned WojtekBoman Jan 30, 2026

WojtekBoman changed the title ~~Adjust home widgets styles~~ [Home Page] Remove Beta Gate for Release 1 Jan 30, 2026

WojtekBoman force-pushed the home-page/remove-beta branch from e0259db to 268d095 Compare January 30, 2026 01:06

WojtekBoman marked this pull request as ready for review January 30, 2026 01:07

WojtekBoman requested review from a team as code owners January 30, 2026 01:07

melvin-bot bot requested review from Ollyws and joekaufmanexpensify and removed request for a team January 30, 2026 01:07

This comment has been minimized.

Sign in to view

mountiny added this to Home page Jan 30, 2026

github-project-automation bot moved this to Backlog in Home page Jan 30, 2026

mountiny moved this from Backlog to In review in Home page Jan 30, 2026

chatgpt-codex-connector bot reviewed Jan 30, 2026

View reviewed changes

WojtekBoman mentioned this pull request Jan 30, 2026

[Home page] [Follow up] Fix opens a chat and load newer messages Pagination test #80982

Open

7 tasks

WojtekBoman force-pushed the home-page/remove-beta branch from 41104bb to 5dc8055 Compare January 30, 2026 02:32

Fix the displayed tab after refresh

9857a20

Add sentry label

2b7f8c5

Add sentry label v2

948d09b

WojtekBoman and others added 5 commits January 30, 2026 14:53

Add fixes to HomePage

550c831

Disable tests for pagination

91d51a8

Replace the thumbupstar image

e7bf8c6

Add sentry label for BaseWidgetItem

7d0fe76

Compress svg

afbb1af

mountiny previously approved these changes Jan 30, 2026

View reviewed changes

adamgrzybowski dismissed mountiny’s stale review via afbb1af January 30, 2026 23:11

ZhenjaHorbach approved these changes Jan 30, 2026

View reviewed changes

mountiny approved these changes Jan 30, 2026

View reviewed changes

mountiny merged commit 4c810b5 into Expensify:main Jan 30, 2026
42 of 46 checks passed

github-project-automation bot moved this from In review to Done in Home page Jan 30, 2026

OSBotify mentioned this pull request Jan 30, 2026

Deploy Checklist: New Expensify 2026-01-28 #80808

Open

mitarachim mentioned this pull request Jan 31, 2026

Home - After logging in via public room and opening announcement link, app returns to login #81089

Open

7 tasks

jponikarchuk mentioned this pull request Jan 31, 2026

Home - "Pay 1 report" is shown after approver leaves workspace #81096

Open

7 tasks

[Home Page] Remove Beta Gate for Release 1 #80965

[Home Page] Remove Beta Gate for Release 1 #80965

Conversation

WojtekBoman commented Jan 30, 2026 • edited by mountiny Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

codecov bot commented Jan 30, 2026 • edited by github-actions bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

github-actions bot commented Jan 30, 2026

Uh oh!

melvin-bot bot commented Jan 30, 2026

Uh oh!

WojtekBoman commented Jan 30, 2026

Uh oh!

This comment has been minimized.

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector bot Jan 30, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot commented Jan 30, 2026

Uh oh!

github-actions bot commented Jan 30, 2026

Uh oh!

mountiny commented Jan 30, 2026

Uh oh!

ZhenjaHorbach commented Jan 30, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

ZhenjaHorbach commented Jan 30, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

jponikarchuk commented Jan 30, 2026

Home - "Pay 1 report" is shown after approver leaves workspace

Action Performed:

Expected Result:

Actual Result:

Workaround:

Platforms:

Screenshots/Videos

Uh oh!

jponikarchuk commented Jan 30, 2026

Inbox - Unending skeleton loader when opening inbox

Action Performed:

Expected Result:

Actual Result:

Workaround:

Platforms:

Screenshots/Videos

Uh oh!

mitarachim commented Jan 30, 2026

Onboarding - "This content is blocked" page opens when invited member opens onboarding

Action Performed:

Expected Result:

Actual Result:

Workaround:

Platforms:

Screenshots/Videos

Uh oh!

github-actions bot commented Jan 30, 2026

Uh oh!

github-actions bot commented Jan 30, 2026

Uh oh!

adamgrzybowski commented Jan 30, 2026

Uh oh!

dannymcclain commented Jan 30, 2026

Uh oh!

WojtekBoman commented Jan 30, 2026 •

edited by mountiny

Loading

codecov bot commented Jan 30, 2026 •

edited by github-actions bot

Loading

ZhenjaHorbach commented Jan 30, 2026 •

edited

Loading

ZhenjaHorbach commented Jan 30, 2026 •

edited

Loading

m-natarajan commented Jan 30, 2026 •

edited

Loading

ZhenjaHorbach commented Jan 30, 2026 •

edited

Loading

ZhenjaHorbach commented Jan 30, 2026 •

edited

Loading