Skip to content

[Due for payment 2026-07-30] [$250] "You appear to be offline" message not shown in RHP chats (report/expense/transaction threads) #94359

Closed

Description

@melvin-bot

Problem

When offline, the You appear to be offline message is shown in regular chats above the composer, but it is not shown in chats opened in the Right-Hand Panel (RHP) — e.g. report threads, expense threads, and transaction threads.

Expected behavior

The You appear to be offline indicator should appear consistently across all chat composers, including RHP chats (report/expense/transaction threads), the same way it does in regular chats. On mobile it already shows on most screens, so behavior should be consistent.

Actual behavior

  • Regular chat: offline message is shown. ✅
  • Report RHP chat: offline message is missing. ❌
  • Expense RHP chat: offline message is missing. ❌

Steps to reproduce

  1. Go offline.
  2. Open a regular chat → observe the You appear to be offline message above the composer.
  3. Open a report/expense/transaction thread in the RHP → notice the message is missing.

Reported in Slack.

Upwork Automation - Do Not Edit
Issue OwnerCurrent Issue Owner: @mallenexpensify

Activity

  1. added
    ExternalAdded to denote the issue can be worked on by a contributor
    Help WantedApply this label when an issue is open to proposals by contributors
    on Jun 23, 2026
  2. melvin-bot commented on Jun 23, 2026

    @melvin-bot
    Author

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @sobitneupane (External)

  3. changed the title [-]"You appear to be offline" message not shown in RHP chats (report/expense/transaction threads)[/-] [+][$250] "You appear to be offline" message not shown in RHP chats (report/expense/transaction threads)[/+] on Jun 23, 2026
  4. melvin-bot commented on Jun 23, 2026

    @melvin-bot
    Author
  5. godzillaxbox19982014-lgtm commented on Jun 23, 2026

    @godzillaxbox19982014-lgtm

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    [$250] "You appear to be offline" message not shown in RHP chats (report/expense/transaction threads)

    What is the root cause of that problem?

    I traced this to the path that handles expense report, You appear to be offline:

    • src/libs/actions/IOU/SplitTransactionUpdate.ts:39 (SplitTransactionUpdate): isPolicyExpenseChat as isPolicyExpenseChatReportUtil,
    • src/libs/actions/IOU/SplitTransactionUpdate.ts:147 (chatReport): const chatReport = allReportsList?.['${ONYXKEYS.COLLECTION.REPORT}${expenseReport?.chatReportID}'];
    • src/libs/actions/IOU/SplitTransactionUpdate.ts:164 (expenseReportParentChat): const expenseReportParentChat = getReportOrDraftReport(chatReport?.parentReportID);
    • The local evidence matches this recurring failure shape: optimistic transaction/report data is written to one Onyx key but the visible list reads another derived key. Here, src/libs/actions/IOU/SplitTransactionUpdate.ts:39 and src/libs/actions/IOU/SplitTransactionUpdate.ts:147 do not agree on the same expense report, You appear to be offline value, so the user-visible path can show a missing or stale state even though nearby data already has the needed context.

    What changes do you think we should make in order to solve the problem?

    • Update src/libs/actions/IOU/SplitTransactionUpdate.ts:39 to derive expense report, You appear to be offline from the report/transaction source that owns this flow before the value is consumed.
    • Carry the same normalized value through src/libs/actions/IOU/SplitTransactionUpdate.ts:147; that follows the safer family move to align optimistic/success/failure data with the selector consumed by the screen, so the write/optimistic/read paths agree instead of only changing the visible component.
    • Keep the change inside the Reports, Expenses, IOU, Transactions surface and avoid changing payment actions, personal/deleted policies.

    What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

    1. Add or update a regression in tests/unit/ReportUtils*.ts for the exact issue flow: [$250] "You appear to be offline" message not shown in RHP chats (report/expense/transaction threads).
    2. Cover the counter-case near src/libs/actions/IOU/SplitTransactionUpdate.ts:39 so valid existing expense report, You appear to be offline behavior still works.
    3. Manually repeat the issue steps after the patch and confirm the visible state/action is no longer stale.

    What alternative solutions did you explore? (Optional)

    • I would not add a broad new condition outside these referenced paths; the safer fix is to keep expense report, You appear to be offline consistent at the first read/write boundary shown above.
  6. lorretheboy commented on Jun 23, 2026

    @lorretheboy
    Contributor

    Proposal

    What is the root cause of that problem?

    The composer's "You appear to be offline" indicator is gated on !shouldUseNarrowLayout:

    const {shouldUseNarrowLayout} = useResponsiveLayout();
    return (
    <ComposerFooter>
    {!shouldUseNarrowLayout && <OfflineIndicator containerStyles={[styles.chatItemComposeSecondaryRow]} />}

    shouldUseNarrowLayout is true not only on small screens but also for any chat opened inside the Right-Hand Panel, because isInNarrowPaneModal is true there:

    const isInNarrowPaneModal =
    // it's a child of the right-docked modal
    activeModalType === CONST.MODAL.MODAL_TYPE.RIGHT_DOCKED ||
    // or there's a "right modal navigator" or "left modal navigator" on the top of the root navigation stack
    // and the component calling this hook is not the child of another modal type, such as a confirm modal
    (isDisplayedInNarrowModalNavigator && !activeModalType);
    const shouldUseNarrowLayout = isSmallScreenWidth || isInNarrowPaneModal;

    The intent of the guard is to avoid a duplicate, since on small screens ScreenWrapper already renders a sticky bottom offline indicator. But that bottom indicator is gated strictly on isSmallScreenWidth, and the wide-screen one defaults to off:

    const displaySmallScreenOfflineIndicator = isSmallScreenWidth && (shouldShowSmallScreenOfflineIndicator ?? showOnSmallScreens ?? true);
    const displayWideScreenOfflineIndicator = !isSmallScreenWidth && (shouldShowWideScreenOfflineIndicator ?? showOnWideScreens ?? false);

    So in a wide-screen RHP thread: isSmallScreenWidth is false → ScreenWrapper shows nothing, while shouldUseNarrowLayout is true → ComposerDefaultFooter hides its own indicator. Nothing renders it anywhere, hence the missing message.

    What changes do you think we should make in order to solve the problem?

    Gate the composer indicator on !isSmallScreenWidth instead of !shouldUseNarrowLayout, so it mirrors exactly the condition under which ScreenWrapper does NOT show the sticky bottom indicator:

    function ComposerDefaultFooter() {
    const styles = useThemeStyles();
    const {shouldUseNarrowLayout} = useResponsiveLayout();
    return (
    <ComposerFooter>
    {!shouldUseNarrowLayout && <OfflineIndicator containerStyles={[styles.chatItemComposeSecondaryRow]} />}
    <ComposerTypingIndicator />
    <ComposerExceededLength />
    </ComposerFooter>
    );

    Use isSmallScreenWidth from useResponsiveLayout (with the existing prefer-shouldUseNarrowLayout-instead-of-isSmallScreenWidth lint-disable comment, as sibling files like ComposerFooter/ComposerSendButton already do). On true mobile the bottom indicator still covers it; on wide-screen RHP threads the composer now renders it; regular wide chats are unchanged.

    The same !shouldUseNarrowLayout guard repeats in every non-composer branch of ReportFooter (archived, anonymous, blocked, system chat, admins-only, read-only), so those RHP footers lose the indicator on wide screens too:

    {!shouldUseNarrowLayout && (
    <View style={styles.offlineIndicatorContainer}>
    <OfflineIndicator containerStyles={[styles.chatItemComposeSecondaryRow]} />
    </View>
    )}

    They should be switched to isSmallScreenWidth for consistency.

    What alternative solutions did you explore? (Optional)

    Have the report's ScreenWrapper opt into shouldShowOfflineIndicatorInWideScreen for RHP threads, letting ScreenWrapper own the indicator everywhere. This is more invasive and risks double indicators in regular wide chats, so fixing the composer guard is cleaner.

  7. nabi-ebrahimi commented on Jun 23, 2026

    @nabi-ebrahimi

    🚨 Edited by proposal-police: This proposal was edited at 2026-06-23 19:41:49 UTC.

    Proposal

    What is the root cause of that problem?

    The composer footer hides its own offline indicator whenever shouldUseNarrowLayout is true:

    function ComposerDefaultFooter() {
    const styles = useThemeStyles();
    const {shouldUseNarrowLayout} = useResponsiveLayout();
    return (
    <ComposerFooter>
    {!shouldUseNarrowLayout && <OfflineIndicator containerStyles={[styles.chatItemComposeSecondaryRow]} />}

    That condition is too broad because shouldUseNarrowLayout is true not only on actual small screens, but also inside RHP / narrow-pane modal routes:

    // it's a child of the right-docked modal
    activeModalType === CONST.MODAL.MODAL_TYPE.RIGHT_DOCKED ||
    // or there's a "right modal navigator" or "left modal navigator" on the top of the root navigation stack
    // and the component calling this hook is not the child of another modal type, such as a confirm modal
    (isDisplayedInNarrowModalNavigator && !activeModalType);
    const shouldUseNarrowLayout = isSmallScreenWidth || isInNarrowPaneModal;

    Regular small-screen chats can rely on the page-level ScreenWrapper offline indicator, but wide-screen RHP chats cannot. ScreenWrapper only shows the default page-level indicator on small screens unless wide-screen display is explicitly enabled:

    /** If there is no bottom content, the mobile offline indicator will stick to the bottom of the screen by default. */
    const displayStickySmallScreenOfflineIndicator = shouldSmallScreenOfflineIndicatorStickToBottom && !bottomContent;
    const displaySmallScreenOfflineIndicator = isSmallScreenWidth && (shouldShowSmallScreenOfflineIndicator ?? showOnSmallScreens ?? true);
    const displayWideScreenOfflineIndicator = !isSmallScreenWidth && (shouldShowWideScreenOfflineIndicator ?? showOnWideScreens ?? false);

    So in RHP report, expense, and transaction-thread chats on wide screens, both possible indicator paths are disabled: the composer footer hides its indicator because RHP makes shouldUseNarrowLayout true, and the surrounding ScreenWrapper does not render the wide-screen offline indicator.

    The same shouldUseNarrowLayout condition is also used in the related non-composer ReportFooter branches, such as archived, anonymous, blocked, system, admins-only, and read-only footers. Those branches should follow the same visibility rule so the offline indicator behavior stays consistent across all report footer states.

    What changes do you think we should make in order to solve the problem?

    Use isSmallScreenWidth for the offline-indicator visibility decision in both ComposerDefaultFooter and the related non-composer ReportFooter branches instead of using shouldUseNarrowLayout.

    The composer/report footer should hide its inline offline indicator only on actual small screens, where the page-level mobile offline indicator already handles the message. It should still render the inline indicator in wide-screen RHP chats, because RHP is a narrow-pane layout but not a small-screen layout.
    This also addresses the duplicate-indicator concern raised during review. On actual small screens, isSmallScreenWidth remains true, so the footer-level indicator stays hidden and the existing mobile behavior is preserved. On wide-screen RHP chats, isSmallScreenWidth is false, so the footer-level indicator is shown where the user is actively composing or viewing the report footer. Based on the latest clarification, the expected behavior is to show the offline indicator for all wide-screen RHP chats, including report, expense, and transaction-thread chats.

    Required change:

    • In src/pages/inbox/report/ReportActionCompose/ComposerDefaultFooter.tsx, destructure isSmallScreenWidth from useResponsiveLayout().
    • Render <OfflineIndicator /> when !isSmallScreenWidth.
    • Keep the existing containerStyles={[styles.chatItemComposeSecondaryRow]} so the visual spacing matches the current wide composer footer.
    • Add the existing lint-disable comment used elsewhere when intentionally reading isSmallScreenWidth.
    • In src/pages/inbox/report/ReportFooter.tsx, destructure isSmallScreenWidth from useResponsiveLayout() together with shouldUseNarrowLayout.
    • Replace the non-composer footer offline indicator checks from !shouldUseNarrowLayout to !isSmallScreenWidth for archived, anonymous, blocked, system, admins-only, and read-only footer branches.
    • Keep using shouldUseNarrowLayout for layout-only spacing such as styles.mb5, because that still depends on the narrow-pane layout.

    Tests that should be added:

    • Add or update a ReportActionCompose UI test that mocks offline network state and useResponsiveLayout() as {shouldUseNarrowLayout: true, isSmallScreenWidth: false, isInNarrowPaneModal: true} and asserts that common.youAppearToBeOffline renders.

    • Add a counter-case for actual small-screen layout {shouldUseNarrowLayout: true, isSmallScreenWidth: true} and assert the composer footer does not render its own inline offline indicator, preventing duplicate mobile indicators.

    • Add coverage for a non-composer ReportFooter state, such as archived or read-only, and assert that the offline indicator renders when {shouldUseNarrowLayout: true, isSmallScreenWidth: false} but not when {shouldUseNarrowLayout: true, isSmallScreenWidth: true}.

    The existing proposal points to src/libs/actions/IOU/SplitTransactionUpdate.ts, but this issue is not caused by optimistic IOU data or transaction/report write paths. The missing UI comes from the composer footer render condition, so changing IOU action logic would not fix the root cause.

    I also considered adding route-specific Wide/Super-Wide RHP logic or enabling the wide-screen ScreenWrapper offline indicator on the RHP report pages, but the latest clarification supports showing the offline indicator for all wide-screen RHP chats. Applying the same isSmallScreenWidth condition in the shared composer and ReportFooter paths keeps the behavior consistent without adding route-specific checks.

    What alternative solutions did you explore? (Optional)

    Fixed Demo:

    Screencast.From.2026-06-25.07-11-12.mp4
  8. github-actions commented on Jun 23, 2026

    @github-actions
    Contributor

    ⚠️ @nabi-ebrahimi Your proposal is a duplicate of an already existing proposal and has been automatically withdrawn to prevent spam. Please review the existing proposals before submitting a new one.

  9. wildan-m commented on Jun 23, 2026

    @wildan-m
    Contributor

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    When offline, the "You appear to be offline." message is shown above the composer in regular chats, but it is missing in chats opened in the Right-Hand Panel (RHP) — report threads, expense threads, and transaction threads.

    What is the root cause of that problem?

    The offline message above the composer is rendered by ComposerDefaultFooter, and it is gated on !shouldUseNarrowLayout:

    return (
    <ComposerFooter>
    {!shouldUseNarrowLayout && <OfflineIndicator containerStyles={[styles.chatItemComposeSecondaryRow]} />}
    <ComposerTypingIndicator />
    <ComposerExceededLength />
    </ComposerFooter>

    The intent of that guard is "only render the composer's offline indicator on a wide screen, because on a small (mobile) screen the indicator is already rendered at the bottom of the screen by ScreenWrapper." However, shouldUseNarrowLayout is true not only on small screens but also whenever the component is inside a narrow-pane modal — i.e. any RHP chat — even on a wide screen. That is by design in useResponsiveLayout, where shouldUseNarrowLayout = isSmallScreenWidth || isInNarrowPaneModal:

    // The component calling this hook is in a "narrow pane modal" if:
    const isInNarrowPaneModal =
    // it's a child of the right-docked modal
    activeModalType === CONST.MODAL.MODAL_TYPE.RIGHT_DOCKED ||
    // or there's a "right modal navigator" or "left modal navigator" on the top of the root navigation stack
    // and the component calling this hook is not the child of another modal type, such as a confirm modal
    (isDisplayedInNarrowModalNavigator && !activeModalType);
    const shouldUseNarrowLayout = isSmallScreenWidth || isInNarrowPaneModal;

    So in an RHP thread on a wide screen, shouldUseNarrowLayout is true, and the composer's offline indicator is hidden. At the same time, ScreenWrapper only renders its own small-screen offline indicator when isSmallScreenWidth is true (and its wide-screen variant defaults to off):

    const displaySmallScreenOfflineIndicator = isSmallScreenWidth && (shouldShowSmallScreenOfflineIndicator ?? showOnSmallScreens ?? true);
    const displayWideScreenOfflineIndicator = !isSmallScreenWidth && (shouldShowWideScreenOfflineIndicator ?? showOnWideScreens ?? false);

    On a wide screen isSmallScreenWidth is false, so ScreenWrapper shows nothing either. The result is that neither the composer nor the screen wrapper shows the offline message in a wide-screen RHP chat — the indicator goes missing. The guard conflates "on mobile" with "in the RHP", but only the "on mobile" case is the one where the bottom ScreenWrapper indicator already covers it.

    What changes do you think we should make in order to solve the problem?

    In ComposerDefaultFooter, change the guard for the composer's offline indicator from !shouldUseNarrowLayout to !isSmallScreenWidth (read isSmallScreenWidth from useResponsiveLayout instead of, or in addition to, shouldUseNarrowLayout).

    With this change:

    • Wide-screen regular chat: isSmallScreenWidth is false → indicator shown (unchanged).
    • Wide-screen RHP chat (report/expense/transaction thread): isSmallScreenWidth is false → indicator now shown (the bug is fixed).
    • Mobile / small screen: isSmallScreenWidth is true → composer indicator hidden, exactly as today, because the bottom ScreenWrapper offline indicator already renders it there (so we avoid a duplicate indicator).

    Because the repo has an ESLint rule preferring shouldUseNarrowLayout over isSmallScreenWidth, this intentional use of isSmallScreenWidth should carry the same // eslint-disable-next-line rulesdir/prefer-shouldUseNarrowLayout-instead-of-isSmallScreenWidth comment that ScreenWrapper already uses for the very same reason (showing the offline indicator based on real screen width, not modal context).

    Compare branch: https://github.com/Expensify/App/compare/main...wildan-m:App:wildan/94359-rhp-composer-offline-indicator?expand=1

    What alternative solutions did you explore? (Optional)

    An alternative is to leave ComposerDefaultFooter as-is and instead enable the wide-screen offline indicator on the RHP's ScreenWrapper (passing shouldShowOfflineIndicatorInWideScreen). This was rejected because it would place the indicator at the bottom of the RHP screen rather than directly above the composer (inconsistent with regular chats, where it sits above the composer), and it would require threading the prop through the report screen wrapper for RHP contexts only. Fixing the guard in the composer footer keeps the indicator in the same place across all chats with a single, localized change.

  10. yusufdeveloper2903 commented on Jun 23, 2026

    @yusufdeveloper2903
    Contributor

    Proposal

    What is the root cause of that problem?

    The composer's offline message is rendered by ComposerDefaultFooter, and it is gated on !shouldUseNarrowLayout:

    https://github.com/Expensify/App/blob/be8591c9249/src/pages/inbox/report/ReportActionCompose/ComposerDefaultFooter.tsx#L11-L15

    const {shouldUseNarrowLayout} = useResponsiveLayout();
    ...
    {!shouldUseNarrowLayout && <OfflineIndicator containerStyles={[styles.chatItemComposeSecondaryRow]} />}

    The problem is what shouldUseNarrowLayout means. In useResponsiveLayout it is true for both small screens and for any component rendered inside the RHP:

    https://github.com/Expensify/App/blob/be8591c9249/src/hooks/useResponsiveLayout/index.ts#L57-L64

    const isInNarrowPaneModal = activeModalType === CONST.MODAL.MODAL_TYPE.RIGHT_DOCKED || (isDisplayedInNarrowModalNavigator && !activeModalType);
    const shouldUseNarrowLayout = isSmallScreenWidth || isInNarrowPaneModal;

    A report/expense/transaction thread opened in the RHP renders the same ReportScreen → ReportFooter → ReportActionCompose → ComposerDefaultFooter, but inside the RIGHT_MODAL_NAVIGATOR, so isInNarrowPaneModal === true and therefore shouldUseNarrowLayout === true even on a wide screen. !shouldUseNarrowLayout is then false and the OfflineIndicator is never mounted in the RHP composer.

    Why the regular (central‑pane) chat works and the RHP one doesn't: on a wide screen the central pane is not in a modal, so isInNarrowPaneModal === false → shouldUseNarrowLayout === false → the composer indicator shows. On true mobile (isSmallScreenWidth === true) the composer indicator is intentionally hidden because ScreenWrapper renders a global small‑screen offline indicator instead — that one is gated on isSmallScreenWidth, not shouldUseNarrowLayout:

    https://github.com/Expensify/App/blob/be8591c9249/src/components/ScreenWrapper/index.tsx#L176-L177

    const displaySmallScreenOfflineIndicator = isSmallScreenWidth && (...);
    const displayWideScreenOfflineIndicator = !isSmallScreenWidth && (... ?? false);  // false for ReportScreen

    ReportScreen passes no offline‑indicator props, so on a wide screen both ScreenWrapper indicators are off and the only source of the composer offline message is ComposerDefaultFooter. In the RHP that source is suppressed by the shouldUseNarrowLayout gate, and no global one replaces it → the message is missing.

    So: RHP composer → isInNarrowPaneModal true → shouldUseNarrowLayout true on wide screen → !shouldUseNarrowLayout false → OfflineIndicator not mounted, and ScreenWrapper's small‑screen indicator is isSmallScreenWidth‑gated (false on wide) → no offline message anywhere → symptom.

    Sibling flows with the identical root cause: the non‑composer footers in ReportFooter (archived / anonymous / blocked / system‑chat / admins‑only / read‑only) use the exact same !shouldUseNarrowLayout gate, so an archived/blocked report opened in the RHP on a wide screen is also missing the indicator — e.g. https://github.com/Expensify/App/blob/be8591c9249/src/pages/inbox/report/ReportFooter.tsx#L120-L122 (repeated at L134-L136, L148-L150, L162-L164, L190-L192, L214-L216). Not affected: central‑pane chats (already wide, indicator shows) and any true mobile screen (the ScreenWrapper small‑screen indicator covers them).

    What changes do you think we should make in order to solve the problem?

    Gate the composer offline indicator on isSmallScreenWidth instead of shouldUseNarrowLayout. That keeps the indicator hidden only on true mobile (where ScreenWrapper shows the global one) and shows it on every wide layout — central pane and RHP. useResponsiveLayout already returns isSmallScreenWidth, and this is exactly the same distinction ScreenWrapper already relies on at L176‑L177 above. The repo already sanctions this with the eslint-disable used in ScreenWrapper/index.tsx#L121-L123.

    1. src/pages/inbox/report/ReportActionCompose/ComposerDefaultFooter.tsx — https://github.com/Expensify/App/blob/be8591c9249/src/pages/inbox/report/ReportActionCompose/ComposerDefaultFooter.tsx#L11-L15

    -    const {shouldUseNarrowLayout} = useResponsiveLayout();
    +    // Use isSmallScreenWidth (not shouldUseNarrowLayout) so the indicator still renders in the RHP on wide screens,
    +    // where ScreenWrapper's small-screen offline indicator is not shown (it is gated on isSmallScreenWidth).
    +    // eslint-disable-next-line rulesdir/prefer-shouldUseNarrowLayout-instead-of-isSmallScreenWidth
    +    const {isSmallScreenWidth} = useResponsiveLayout();
    ...
    -            {!shouldUseNarrowLayout && <OfflineIndicator containerStyles={[styles.chatItemComposeSecondaryRow]} />}
    +            {!isSmallScreenWidth && <OfflineIndicator containerStyles={[styles.chatItemComposeSecondaryRow]} />}

    2. (Consistency) src/pages/inbox/report/ReportFooter.tsx — apply the same !shouldUseNarrowLayout → !isSmallScreenWidth change to the 6 non‑composer footer branches (L120-L122, L134-L136, L148-L150, L162-L164, L190-L192, L214-L216) so archived/blocked/system/admins‑only/read‑only threads in the RHP are consistent too. useResponsiveLayout is already called here (it destructures shouldUseNarrowLayout at https://github.com/Expensify/App/blob/be8591c9249/src/pages/inbox/report/ReportFooter.tsx#L56) — just also pull isSmallScreenWidth (with the same eslint‑disable) and swap the gate.

    Verify:

    • Wide screen, regular chat, offline → message shows (unchanged). ✅
    • Wide screen, report/expense/transaction thread in RHP, offline → message now shows. ✅
    • Mobile (small screen), any chat, offline → composer indicator stays hidden, ScreenWrapper's global small‑screen indicator shows (no duplicate). ✅

    What alternative solutions did you explore? (Optional)

    Enable the ScreenWrapper wide‑screen indicator for ReportScreen by passing shouldShowOfflineIndicatorInWideScreen (drives displayWideScreenOfflineIndicator at https://github.com/Expensify/App/blob/be8591c9249/src/components/ScreenWrapper/index.tsx#L177). Rejected: it would render a second indicator in the central pane (the composer footer already shows one there), and it places the message at the screen bottom rather than directly above the composer where the existing design puts it.

    Add isInNarrowPaneModal to the gate (!shouldUseNarrowLayout || isInNarrowPaneModal). This works functionally but is a double negative that re‑expands to "show unless small screen", i.e. exactly !isSmallScreenWidth — the direct form is clearer and matches how ScreenWrapper already decides small‑ vs wide‑screen indicators.

  11. github-actions commented on Jun 23, 2026

    @github-actions
    Contributor

    ⚠️ @yusufdeveloper2903 Thanks for your proposal. Please update it to follow the proposal template, as proposals are only reviewed if they follow that format (note the mandatory sections).

  12. abbasifaizan70 commented on Jun 23, 2026

    @abbasifaizan70
    Contributor

    🚫 Duplicated proposal withdrawn by 🤖 ProposalPolice.

  13. 64 remaining items

  14. melvin-bot commented on Jul 29, 2026

    @melvin-bot
    Author

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  15. melvin-bot commented on Jul 29, 2026

    @melvin-bot
    Author

    Payment Summary

    Upwork Job

    BugZero Checklist (@mallenexpensify)

    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants/2069504855594848967/hired)
    • I have verified the PR was not reverted
    • I have applied any discounts due to bugs/regressions introduced by this PR
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  16. sobitneupane commented on Jul 30, 2026

    @sobitneupane
    Contributor

    BugZero 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.

      I believe we intentionally chose not to show the offline indicator on RHP chats before because it is already visible in the background.

    • [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.

    • [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

      Link to issue: https://github.com/Expensify/Expensify/issues/668129

    Regression Test Proposal

    Test:

    1. Go offline.
    2. Open a regular chat → observe the You appear to be offline message above the composer.
    3. Open a report/expense/transaction thread in the RHP → Verify that offline message is shown.

    Do we agree 👍 or 👎

    Zapier Logs Run ID: 00040eee-5d13-a28e-dcb3-9141ed555cd4
  17. melvin-bot commented on Aug 3, 2026

    @melvin-bot
    Author

    @mallenexpensify Huh... This is 4 days overdue. Who can take care of this?

  18. mallenexpensify commented on Aug 4, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor: @lorretheboy paid $250 via Upwork
    Contributor+: @sobitneupane due $250 via NewDot

    @lorretheboy can you please accept the job below? Please reply here and tag me once you have.
    If you're not sent an offer in Upwork when you're assigned to an issue, please tag me. If an Upwork job exists, please submit a proposal.
    https://www.upwork.com/jobs/~022084460683290926021

    ^ Test case created. Thx

  19. lorretheboy commented on Aug 4, 2026

    @lorretheboy
    Contributor

    @mallenexpensify Thx, I accepted

  20. added and removed on Aug 4, 2026
  21. mallenexpensify commented on Aug 5, 2026

    @mallenexpensify
    Contributor

    @lorretheboy paid, summary updated above. Thx.

  22. JmillsExpensify commented on Sep 18, 2026

    @JmillsExpensify
    Contributor

    $250 approved for @sobitneupane

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 productionDailyKSv2ExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions