You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-09-04] [Exploratory] iOS - The screen flickers when tapping the Cancel button to exit edit mode #97768
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:
Open the app
Open any chat and send a message
Long-press → Edit comment.
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
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:
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:
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
Activity
applause-bot commentedon Aug 4, 2026
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
mukhrr commentedon Aug 21, 2026
@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, hardcodedtrue. On cancel the composer never lost focus, sofocusComposerWithDelaytakes the already-focused branch and, 150 ms later (CONST.COMPOSER_FOCUS_DELAY), callsrequestKeyboardForFocusedComposerinstead of doing nothing. That helper only exists inindex.native.ts, and on iOSKeyboardController.setFocusTo('current')runs: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.
handleEditFocusalready readseditingState:const handleEditFocus = useCallback(() => { - focus(true, undefined, true); + focus(true, undefined, editingState === CONST.REPORT_ACTION_EDIT_MESSAGE_STATE.EDITING); onFocus();editingStatewas already in thatuseCallbackdep array, so it's a one-expression change. Entry keeps the forced path (the Android case the flag exists for). Save exits through the samestopEditing()→OFFbranch, so it's covered too. Web and desktop are unaffected,requestKeyboardForFocusedComposeris a no-op theremelvin-bot commentedon Aug 24, 2026
Current assignee @hoangzinh is eligible for the External assigner, not assigning anyone new.
melvin-bot commentedon Aug 24, 2026
Unable to auto-create job on Upwork. The BZ team member should create it manually for this issue.
blimpich commentedon Aug 24, 2026
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.
mukhrr commentedon Aug 25, 2026
@blimpich I am paid through ND. thanks
15 remaining items
melvin-bot commentedon Sep 3, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)melvin-bot commentedon Sep 3, 2026
Payment Summary
Resolving PRs:
[Exploratory] iOS - Fix screen flicker when tapping Cancel to exit edit mode #99398
Reviewer: @hoangzinh owed $250 via NewDot
Reviewer: @mukhrr owed $250 via NewDot
BugZero Checklist (@mallenexpensify)
mukhrr commentedon Sep 8, 2026
@mallenexpensify this is $150
melvin-bot commentedon Sep 8, 2026
@mallenexpensify Eep! 4 days overdue now. Issues have feelings too...
mallenexpensify commentedon Sep 8, 2026
Payment Summary
Contributor: @mukhrr due $150 via NewDot
Contributor+: @hoangzinh due $150 via NewDot
laurenreidexpensify commentedon Sep 10, 2026
$150 approved @hoangzinh New Expensify
flaviadefaria commentedon Sep 11, 2026
Approved: @mukhrr owed $150 via NewDot