Skip to content

fix: Empty space is shown when clearing the cache#84014

Open
suhailpthaj wants to merge 3 commits intoExpensify:mainfrom
suhailpthaj:fix/76666
Open

fix: Empty space is shown when clearing the cache#84014
suhailpthaj wants to merge 3 commits intoExpensify:mainfrom
suhailpthaj:fix/76666

Conversation

@suhailpthaj
Copy link
Copy Markdown
Contributor

Explanation of Change

In this PR, we are solving the empty space appearing in the chat after clearing the cache or re-signing issue.

Fixed Issues

$ #76666
PROPOSAL: #76666 (comment)

Tests

  1. Launch the app or open https://staging.new.expensify.com.
  2. Go to Account -> Troubleshoot.
  3. Press Clear cache and restart then confirm.
  4. Go to LHN, select any chat.
  5. Verify that the loading skeleton appears along with the last message instead of the empty space which was appearing before.
  • Verify that no errors appear in the JS console

Offline tests

Same as Test

QA Steps

Same as Test

  • 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
  • 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
Android-native.mp4
Android: mWeb Chrome
Android-mWeb.mov
iOS: Native
iOS-native.mp4
iOS: mWeb Safari
iOS-mWeb.mp4
MacOS: Chrome / Safari
macOS.mp4

@suhailpthaj suhailpthaj requested review from a team as code owners March 3, 2026 10:08
@melvin-bot melvin-bot bot requested review from heyjennahay and sobitneupane and removed request for a team March 3, 2026 10:08
@melvin-bot
Copy link
Copy Markdown

melvin-bot bot commented Mar 3, 2026

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

@melvin-bot melvin-bot bot removed the request for review from a team March 3, 2026 10:08
Copy link
Copy Markdown

@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: 1b7dda90ed

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

@suhailpthaj
Copy link
Copy Markdown
Contributor Author

@codex review

Copy link
Copy Markdown

@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: 2fcfddc527

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

Comment on lines +800 to +802
const reportActionsToRender = useMemo(
() => (isWaitingForInitialLoad && lastAction ? [lastAction] : sortedVisibleReportActions),
[isWaitingForInitialLoad, lastAction, sortedVisibleReportActions],
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Preserve scroll-target action during initial loading fallback

When isWaitingForInitialLoad is true, this narrows data to only lastAction, which can drop the action referenced by reportActionID (initialScrollKey) even if it already exists in sortedVisibleReportActions. Because InvertedFlatList initializes its scroll-key state from the first data snapshot, starting with a list that omits the target causes linked-message/deep-link opens to lose their intended anchor once full data arrives, so users can land on the wrong part of the conversation during initial load.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@sobitneupane we shouldn't apply this as this case isn't practically possible I believe.

When user clears the cache or re-sign then the jump happened but when user navigated with deep link in either the same tab or in a different one then it will trigger the full page refresh which will show the complete page loading and that empty jump wouldn't happen then. So it's practically not possible to get us on Empty space when deep link or reportActionID is there in deep link.

You can test this on staging because this is the case which is expected on staging too. As we only have last action available (ocassionally with some sort of messages) when the empty space appears. I'm expecting that the deep linking anchoring is already there otherwise how we are anchoring the deep links when there is empty space?

@codecov
Copy link
Copy Markdown

codecov bot commented Mar 3, 2026

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines Coverage Δ
src/pages/inbox/report/ReportActionsList.tsx 78.59% <100.00%> (+0.25%) ⬆️
... and 9 files with indirect coverage changes

@suhailpthaj
Copy link
Copy Markdown
Contributor Author

@heyjennahay @sobitneupane Bump for PR review.

@sobitneupane The codex suggestion is an edge case which I'll handle but you can continue reviewing the PR.

@sobitneupane
Copy link
Copy Markdown
Contributor

sobitneupane commented Mar 11, 2026

The codex suggestion is an edge case which I'll handle but you can continue reviewing the PR.

@suhailpthaj When do you expect to handle this? It would be very helpful if you could address it before the review. Also, could you please merge main?

Copy link
Copy Markdown
Contributor

@heyjennahay heyjennahay left a comment

Choose a reason for hiding this comment

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

Bug fix 👍

@suhailpthaj
Copy link
Copy Markdown
Contributor Author

@sobitneupane Responded on the edge case, can you have a look?

Copy link
Copy Markdown
Contributor

@sobitneupane sobitneupane left a comment

Choose a reason for hiding this comment

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

@suhailpthaj I noticed a couple of issues in the PR:

  1. Screen Flicker: In the screen recrding below, the report initially renders with a few actions along with the header. Shortly after, it gets replaced by the last report action with a skeleton.
Untitled.copy.mov
  1. Skeleton overlaping animation.
Image

@sobitneupane
Copy link
Copy Markdown
Contributor

@suhailpthaj when a user is offline, we show a few report actions along with a loading skeleton (and in some cases, full report). When the user goes online, this gets replaced by the last report action along with the loading skeleton.

Screen.Recording.2026-03-24.at.18.00.38.mov
Untitled.mov

I can still see blank spaces above few report actions on slow internet.

Untitled.copy1.mov

@sobitneupane
Copy link
Copy Markdown
Contributor

Bump @suhailpthaj

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.

3 participants