Skip to content

[Due for payment 2026-09-04] [Exploratory] iOS - The screen flickers when tapping the Cancel button to exit edit mode #97768

Closed

Description

@applause-bot

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.


Version Number: 9.4.49.1
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #97418
Email or phone of affected tester (no customers): n/a
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: iPhone 13 iOS 26.5
App Component: Chat Report View

Action Performed:

  1. Open the app
  2. Open any chat and send a message
  3. Long-press → Edit comment.
  4. Tap the cancel (X) button

Expected Result:

The screen should not flicker when tapping the Cancel button when editing a message

Actual Result:

The screen flickers when tapping the Cancel button to exit edit mode

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome Safari

Screenshots/Videos

Bug7225338_1785828623919.ScreenRecording_08-04-2026_02-21-26_1.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7225338

Issue OwnerCurrent Issue Owner: @mallenexpensify

Activity

  1. applause-bot commented on Aug 4, 2026

    @applause-bot
    Author

    While Applause doesn't embed attachments for this bug, here are the links for quick view:
    https://platform.applause.com/services/links/v1/external/65c76ca5940e92cfdb9d7452039c699681f705bf36cae307cc4180ad169090bb

  2. mukhrr commented on Aug 21, 2026

    @mukhrr
    Contributor

    @blimpich QA found this while testing our PR here. Is it okay for me and @hoangzinh to take care of this?

    RCA

    Leaving edit mode re-focuses the main composer:

    useEditComposerToggle.ts#L102-L105 → onFocus?.() → handleEditFocus → focus(true, undefined, true)

    That third arg is forceKeyboardIfAlreadyFocused, hardcoded true. On cancel the composer never lost focus, so focusComposerWithDelay takes the already-focused branch and, 150 ms later (CONST.COMPOSER_FOCUS_DELAY), calls requestKeyboardForFocusedComposer instead of doing nothing. That helper only exists in index.native.ts, and on iOS KeyboardController.setFocusTo('current') runs:

    input?.inputView = nil
    input?.reloadInputViews()
    input?.focus()

    So an already-visible keyboard gets torn down and rebuilt for a field that was already focused, and the report list renders wrong for one frame. The flag was added for Android in 489139080be; iOS just inherits it.

    Measured (my sim run, iOS 26.5): cancel lands at 37.303 s, the report list renders completely blank at 37.497 s (194 ms later) for a single 13 ms frame, normal again at 37.510 s. The reporter's video shows the same signature: 167 ms gap, one 33 ms frame.

    Solution

    Only force the keyboard on the way into edit mode. handleEditFocus already reads editingState:

     const handleEditFocus = useCallback(() => {
    -    focus(true, undefined, true);
    +    focus(true, undefined, editingState === CONST.REPORT_ACTION_EDIT_MESSAGE_STATE.EDITING);
         onFocus();

    editingState was already in that useCallback dep array, so it's a one-expression change. Entry keeps the forced path (the Android case the flag exists for). Save exits through the same stopEditing() → OFF branch, so it's covered too. Web and desktop are unaffected, requestKeyboardForFocusedComposer is a no-op there

  3. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Aug 24, 2026
  4. melvin-bot commented on Aug 24, 2026

    @melvin-bot

    Current assignee @hoangzinh is eligible for the External assigner, not assigning anyone new.

  5. melvin-bot commented on Aug 24, 2026

    @melvin-bot

    Unable to auto-create job on Upwork. The BZ team member should create it manually for this issue.

  6. blimpich commented on Aug 24, 2026

    @blimpich
    Contributor

    Talked with @mukhrr about this in DM. Payout for this issue should be $150. For some reason the automation was not able to create the job in upwork.

  7. mukhrr commented on Aug 25, 2026

    @mukhrr
    Contributor

    @blimpich I am paid through ND. thanks

  8. 15 remaining items

  9. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Sep 3, 2026
  10. melvin-bot commented on Sep 3, 2026

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  11. melvin-bot commented on Sep 3, 2026

    @melvin-bot

    Payment Summary

    Resolving PRs:

    BugZero Checklist (@mallenexpensify)

    • I have confirmed assignees, roles, and Upwork contracts look correct
    • I have paid out Upwork contracts / manual NewDot requests
    • [BugZero Assignee] I have created a GH issue for creating/updating the regression test once above steps have been agreed upon
  12. mukhrr commented on Sep 8, 2026

    @mukhrr
    Contributor

    @mallenexpensify this is $150

    Talked with @mukhrr about this in DM. Payout for this issue should be $150. For some reason the automation was not able to create the job in upwork.

  13. melvin-bot commented on Sep 8, 2026

    @melvin-bot

    @mallenexpensify Eep! 4 days overdue now. Issues have feelings too...

  14. mallenexpensify commented on Sep 8, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor: @mukhrr due $150 via NewDot
    Contributor+: @hoangzinh due $150 via NewDot

  15. laurenreidexpensify commented on Sep 10, 2026

    @laurenreidexpensify
    Contributor

    $150 approved @hoangzinh New Expensify

  16. flaviadefaria commented on Sep 11, 2026

    @flaviadefaria
    Contributor

    Approved: @mukhrr owed $150 via NewDot

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 contributorNot a priority

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions