Skip to content

Fix: Offline message not displayed when opening video in Chat while offline#89786

Open
nabi-ebrahimi wants to merge 8 commits into
Expensify:mainfrom
nabi-ebrahimi:fix/chat-offline-message-missing-video-open
Open

Fix: Offline message not displayed when opening video in Chat while offline#89786
nabi-ebrahimi wants to merge 8 commits into
Expensify:mainfrom
nabi-ebrahimi:fix/chat-offline-message-missing-video-open

Conversation

@nabi-ebrahimi
Copy link
Copy Markdown
Contributor

@nabi-ebrahimi nabi-ebrahimi commented May 6, 2026

Explanation of Change

These changes prevent remote video attachments from trying to load while the user is offline. Instead, the attachment modal shows an offline blocking view, hides attachment actions like download and the three-dot menu, and avoids rendering the video content until connectivity is restored.

This gives users clearer feedback when a video cannot be accessed offline, instead of showing a broken or stuck attachment preview.

Fixed Issues

$ #88216
PROPOSAL: #88216 (comment)

Tests

  1. Navigate to any chat
  2. Upload a video
  3. Disable the internet connection via troubleshoot
  4. Click on the video
  5. Verify that an offline message is displayed and download option is not displayed
  • Verify that no errors appear in the JS console

Offline tests

Same as Tests.

QA Steps

Same as Tests.

// TODO: These must be filled out, or the issue title must include "[No QA]."

  • 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 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
Screen.Recording.2026-05-07.at.2.00.10.AM.mov
Android: mWeb Chrome
Screen.Recording.2026-05-06.at.11.52.35.PM.mov
iOS: Native
Screen.Recording.2026-05-07.at.12.08.51.PM.mov
iOS: mWeb Safari
Screen.Recording.2026-05-11.at.1.56.07.PM.mov
MacOS: Chrome / Safari
Screen.Recording.2026-05-07.at.11.59.10.AM.mov

@codecov
Copy link
Copy Markdown

codecov Bot commented May 6, 2026

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 Δ
...HTMLEngineProvider/HTMLRenderers/VideoRenderer.tsx 95.00% <100.00%> (ø)
src/libs/AttachmentUtils.ts 100.00% <100.00%> (ø)
...een/routes/report/ReportAttachmentModalContent.tsx 97.05% <100.00%> (ø)
...rc/components/Attachments/AttachmentView/index.tsx 52.84% <40.00%> (-0.10%) ⬇️
src/components/VideoPlayerPreview/index.tsx 2.12% <0.00%> (-0.32%) ⬇️
... and 21 files with indirect coverage changes

@nabi-ebrahimi nabi-ebrahimi marked this pull request as ready for review May 7, 2026 08:05
@nabi-ebrahimi nabi-ebrahimi requested review from a team as code owners May 7, 2026 08:05
@melvin-bot melvin-bot Bot requested review from Ollyws and heyjennahay May 7, 2026 08:05
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented May 7, 2026

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

@melvin-bot melvin-bot Bot removed request for a team May 7, 2026 08:05
Comment thread src/components/Attachments/AttachmentView/index.tsx Outdated
@nabi-ebrahimi
Copy link
Copy Markdown
Contributor Author

@Ollyws, friendly bump. thanks.

@Ollyws
Copy link
Copy Markdown
Contributor

Ollyws commented May 12, 2026

Will get to this asap.

// Skip API root normalization for search attachments because this route is only opened from preview,
// which already passes a resolved source. Keep normalization for other types to support email entry points.
const source = getValidatedImageSource(sourceParam, type !== CONST.ATTACHMENT_TYPE.SEARCH);
const fileName = originalFileName ?? (typeof source === 'string' ? getFileName(source) : '');
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Could you explain this line?

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.

We need this because the modal offline-video check was not working reliably when originalFileName was missing. AttachmentModalBaseContent uses this value to create file.name, and AttachmentView uses file.name to detect video attachments. Without this fallback, the modal can fail to recognize the attachment as a video and skip the offline handling.

const attrHref = htmlAttribs[CONST.ATTACHMENT_SOURCE_ATTRIBUTE] || htmlAttribs.src || htmlAttribs.href || '';
const sourceURL = tryResolveUrlFromApiRoot(attrHref);
const fileName = getFileName(`${sourceURL}`);
const fileName = htmlAttribs[CONST.ATTACHMENT_ORIGINAL_FILENAME_ATTRIBUTE] || getFileName(`${sourceURL}`);
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

And this one.

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.

We need this because the route was sometimes passing a filename derived from an opaque attachment URL, so the modal could fail to detect the attachment as a video. The actual uploaded filename is available in the HTML data-name attribute, so passing that as originalFileName makes the modal’s video/offline logic reliable.

@nabi-ebrahimi
Copy link
Copy Markdown
Contributor Author

@Ollyws I need one clarification.

This PR currently fixes the attachment modal behavior so the offline view is shown when opening a video while offline.

However, in the chat view itself, the same video can still be played while offline from the preview. Should this PR also block offline video playback directly in chat, or is the expected scope only the attachment modal? Thanks

REC-20260514103200.mp4

@nabi-ebrahimi
Copy link
Copy Markdown
Contributor Author

@Ollyws, could you please check this comment, when you get a chance. thanks.

@nabi-ebrahimi
Copy link
Copy Markdown
Contributor Author

@Ollyws, gentle bump. thanks.

@Ollyws
Copy link
Copy Markdown
Contributor

Ollyws commented May 18, 2026

@nabi-ebrahimi Yeah I think it would be best if the same behaviour applied to the preview, i.e it's disabled using the same conditions.

@nabi-ebrahimi
Copy link
Copy Markdown
Contributor Author

@Ollyws I’ve updated this as well, so the offline indicator is now shown in the chat preview using the same conditions as the modal. Could you please take another look when you get a chance? Thanks!

@nabi-ebrahimi
Copy link
Copy Markdown
Contributor Author

@Ollyws, gentle bump. thanks.

accessibilityLabel={fileName}
isDeleted={isDeleted}
/>
{shouldShowOfflineVideoIndicator && <AttachmentOfflineIndicator isPreview />}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think this would be better inside the VideoPlayerThumbnail component, as let's make sure it retains the same style, as now it just sits over the top of the image and doesn't have the same border:

Image

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.

2 participants