Repository navigation
Description
Problem
Same as #158961 on iOS 18.2 (I'm creating this new issue in case of confusion with the original issue).
This PR reverted the workaround to fixed the original issue on iOS 26, so the original issue will reappear.
Why we revert the workaround
Because the workaround doesn't work anymore. It caused our whole gesture blocking system to fail completely (see this issue). We have to revert it and find other solutions.
This is ultimately an Apple bug and we already filed a radar: #159814. We should escalate to Apple.
Based on the timing of report, it may be beta 6, but I am not 100% sure (could be earlier betas)
Internal issue: b/448900829
Updates
Since the thread is getting long, I will post important updates here.
2026-01-09
The primary issue causing WebViews to become unresponsive to tap interactions on iOS 26 has been resolved via a hotfix and is available on stable 3.38.6.
The current fix in stable does not yet resolve "touch fall-through" scenarios (#175099 (comment) and #179916). You may still experience issues where taps on Flutter overlays (such as Drawers or Dropdowns) incorrectly pass through to the underlying WebView.
I am actively developing a more comprehensive architectural update using hit testing to address these remaining fall-through cases (design doc). This solution should fix the non-tappable web view issue for good (unlike the quick fix which could break again in future iOS versions).
If you only have the unresponsive WebView issue, upgrade to stable 3.38.6. If you urgently need the fall-through fix, see the instructions to cherry-pick the draft hitTest implementation.
Activity
[ios]Do not re-adds delaying recognizer on iOS 26 (#175097)
[ios]Do not re-adds delaying recognizer on iOS 26 (flutter#175097)
[ios]Do not re-adds delaying recognizer on iOS 26 (flutter#175097)
[ios]Do not re-adds delaying recognizer on iOS 26 (flutter#175097)
[ios]Do not re-adds delaying recognizer on iOS 26 (flutter#175097)
[ios]Do not re-adds delaying recognizer on iOS 26 (flutter#175097)
AlexDochioiu commentedon Sep 26, 2025
temaand1 commentedon Sep 30, 2025
ilikebasic commentedon Sep 30, 2025
Workaround: Wrap all widgets which show on top of the WebView with PointerInterceptor (pointer_interceptor plugin on pub.dev).
RemcodM commentedon Sep 30, 2025
I think
pointer_interceptoris meant to prevent clicks to the underlying webview. The problem here is that the webview element does not accept taps at all, regardless if any element is drawn over it.pointer_interceptorseems unrelated here.116 remaining items
Make the WebView non-clickable and let PointerInterceptor handle the …
hellohuanlin commentedon Jan 30, 2026
Can you explain more on your special scenario and how it doesn't work?
[pv]add integration test for original untappable web view link behind…
[pv]add integration test for original untappable web view link behind…
[pv]add integration test for original untappable web view link behind…
[ios][platform_view]Reland hitTest approach (with a few 2026 update) (#…
[ios][platform_view]Reland hitTest approach (with a few 2026 update) (f…
Reverts "[ios][platform_view]Reland hitTest approach (with a few 2026…
[ios][pv] Reland platform view hitTest approach (again) (flutter#185126)
hellohuanlin commentedon Apr 21, 2026
I have exciting news to share -
Following the radar we filed with Apple, we've successfully collaborated with the WebKit team to resolve the issue. A fix has been officially implemented as of iOS 26.4 (and I just confirmed it working).
We recently landed the hitTest approach, which fixes a few more touch fall-through issues, and help prevent regressions even if this WebKit bug happens again (or similar bugs in other platform views)
Next step: we will skip our temp workarounds on iOS 26.4 since it's not needed anymore: #185372
fondoger commentedon Apr 22, 2026
cholder00 commentedon Apr 29, 2026
thank you very much for your contribution.ser
github-actions commentedon May 24, 2026
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.