[CP Staging] fix: start chat page is broken after refreshing the page by nkdengineer · Pull Request #59378 · Expensify/App

nkdengineer · 2025-03-31T15:16:01Z

Explanation of Change

fix: start chat page is broken after refreshing the page

Fixed Issues

$ #59352
PROPOSAL: #59352 (comment)

Tests

Precondition:

Desktop app is installed

Create a workspace if we don't have
Open FAB > Start chat
Refresh the page
Verify that the start chat page isn't broken

Verify that no errors appear in the JS console

Offline tests

None

QA Steps

Precondition:

Desktop app is installed

Create a workspace if we don't have
Open FAB > Start chat
Refresh the page
Verify that the start chat page isn't broken

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Screen.Recording.2025-03-31.at.22.10.18.mov

Android: mWeb Chrome

Screen.Recording.2025-03-31.at.22.08.53.mov

iOS: Native

Screen.Recording.2025-03-31.at.22.10.44.mov

iOS: mWeb Safari

Screen.Recording.2025-03-31.at.22.07.53.mov

MacOS: Chrome / Safari

Screen.Recording.2025-03-31.at.22.06.34.mov

MacOS: Desktop

Screen.Recording.2025-03-31.at.22.11.07.mov

melvin-bot · 2025-03-31T15:25:03Z

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

github-actions · 2025-03-31T19:18:44Z

🚧 @grgia has triggered a test app build. You can view the workflow run here.

github-actions · 2025-03-31T20:13:54Z

🧪🧪 Use the links below to test this adhoc build on Android, iOS, Desktop, and Web. Happy testing! 🧪🧪

Android 🤖	iOS 🍎
Android 🤖🔄	iOS 🍎🔄
https://ad-hoc-expensify-cash.s3.amazonaws.com/android/59378-hybrid/index.html	https://ad-hoc-expensify-cash.s3.amazonaws.com/ios/59378-hybrid/index.html

Desktop 💻	Web 🕸️
https://ad-hoc-expensify-cash.s3.amazonaws.com/desktop/59378/NewExpensify.dmg	https://59378.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

brunovjk · 2025-03-31T22:17:29Z

reviewing

brunovjk · 2025-04-01T01:36:52Z

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: Native
- Android: mWeb Chrome
- iOS: Native
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
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: Native

59378_android_native.mov

Android: mWeb Chrome

59378_android_web.mov

iOS: Native

59378_ios_native.mov

iOS: mWeb Safari

59378_ios_web.mov

MacOS: Chrome / Safari

59378_web_chrome.mov

MacOS: Desktop

59378_web_desktop.mov

brunovjk

LGTM. I was unable to reproduce the bug on all platforms, but where I was able to reproduce it this PR fixed it and did not introduce any bugs or crashes in my tests.

brunovjk · 2025-04-01T01:47:07Z

All yours @JS00001 :D

OSBotify · 2025-04-01T09:31:19Z

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

fix: start chat page is broken after refreshing the page (cherry picked from commit e79a743) (CP triggered by mountiny)

github-actions · 2025-04-01T11:14:38Z

🚀 Cherry-picked to staging by https://github.com/mountiny in version: 9.1.21-3 🚀

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

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

github-actions · 2025-04-01T15:03:08Z

🚀 Deployed to production by https://github.com/grgia in version: 9.1.21-3 🚀

platform	result
🖥 desktop 🖥	success ✅
🕸 web 🕸	success ✅
🤖 android 🤖	failure ❌
🍎 iOS 🍎	success ✅

nkdengineer added 2 commits March 31, 2025 22:12

fix: start chat page is broken after refreshing the page

80cfde6

run prettier

0f7ddb7

nkdengineer force-pushed the fix/59352 branch from 402e8a1 to 0f7ddb7 Compare March 31, 2025 15:22

nkdengineer marked this pull request as ready for review March 31, 2025 15:24

nkdengineer requested a review from a team as a code owner March 31, 2025 15:24

melvin-bot bot requested a review from brunovjk March 31, 2025 15:25

melvin-bot bot removed the request for review from a team March 31, 2025 15:25

nkdengineer mentioned this pull request Mar 31, 2025

[Due for payment 2025-04-10] [Due for payment 2025-04-08] [$250] Start chat - Start chat page is broken after refreshing the page #59352

Closed

8 tasks

JS00001 self-requested a review March 31, 2025 15:27

brunovjk approved these changes Apr 1, 2025

View reviewed changes

grgia approved these changes Apr 1, 2025

View reviewed changes

grgia merged commit e79a743 into Expensify:main Apr 1, 2025
17 checks passed

mountiny changed the title ~~fix: start chat page is broken after refreshing the page~~ [CP Staging] fix: start chat page is broken after refreshing the page Apr 1, 2025

OSBotify pushed a commit that referenced this pull request Apr 1, 2025

Merge pull request #59378 from nkdengineer/fix/59352

748f1e5

fix: start chat page is broken after refreshing the page (cherry picked from commit e79a743) (CP triggered by mountiny)

github-actions bot added the CP Staging marks PRs that have been CP'd to staging label Apr 1, 2025

github-actions bot mentioned this pull request Apr 1, 2025

Deploy Checklist: New Expensify 2025-03-31 #59334

Closed

62 tasks

hoangzinh mentioned this pull request Sep 12, 2025

Fix autofocus issue on closing side panel #70097

Merged

51 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[CP Staging] fix: start chat page is broken after refreshing the page#59378

[CP Staging] fix: start chat page is broken after refreshing the page#59378
grgia merged 2 commits intoExpensify:mainfrom
nkdengineer:fix/59352

nkdengineer commented Mar 31, 2025

Uh oh!

melvin-bot bot commented Mar 31, 2025

Uh oh!

github-actions bot commented Mar 31, 2025

Uh oh!

github-actions bot commented Mar 31, 2025

Uh oh!

brunovjk commented Mar 31, 2025

Uh oh!

brunovjk commented Apr 1, 2025

Uh oh!

brunovjk left a comment

Uh oh!

brunovjk commented Apr 1, 2025

Uh oh!

Uh oh!

OSBotify commented Apr 1, 2025

Uh oh!

github-actions bot commented Apr 1, 2025

Uh oh!

github-actions bot commented Apr 1, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Conversation

nkdengineer commented Mar 31, 2025

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

melvin-bot bot commented Mar 31, 2025

Uh oh!

github-actions bot commented Mar 31, 2025

Uh oh!

github-actions bot commented Mar 31, 2025

Uh oh!

brunovjk commented Mar 31, 2025

Uh oh!

brunovjk commented Apr 1, 2025

Reviewer Checklist

Screenshots/Videos

Uh oh!

brunovjk left a comment

Choose a reason for hiding this comment

Uh oh!

brunovjk commented Apr 1, 2025

Uh oh!

Uh oh!

OSBotify commented Apr 1, 2025

Uh oh!

github-actions bot commented Apr 1, 2025

Uh oh!

github-actions bot commented Apr 1, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants