iOS 26 – WebView/Custom Widget becomes completely unresponsive after interacting with any Flutter UI element

[laurapoupette]

Can we access your project?

• I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

Initial behavior:
When the map page opens, the HERE map works correctly. Touch interactions, pan and map interactions are responsive.

Problem:
As soon as the user interacts with another Flutter UI element, then returns to the map, the WebView/map no longer receives touch interactions.

We reproduced the issue after several different actions, including:

• opening and closing the Flutter Drawer;
• opening a partner detail;
• using the partner search;
• opening/closing Flutter UI elements over the map.

After returning to the map, the map remains visually displayed and the JavaScript/WebView is still running, but touch interactions are frozen.

The problem is not specific to the Drawer: virtually any interaction that switches interaction between the WebView and Flutter UI can trigger it.

Expected Behavior

Since FlutterFlow currently uses Flutter 3.38.6 for our project, we would like to know:

1. Is FlutterFlow aware of this remaining iOS 26 PlatformView/WebView gesture issue?
2. Is a Flutter/FlutterFlow update containing the upstream fix planned soon?
3. Is there a FlutterFlow-compatible workaround that can be applied without manually modifying the exported iOS project?
4. If not, would you recommend applying the native iOS gesture-recognizer blocking policy patch to the exported project for production?

This is currently blocking the release of our iOS application because the main map becomes unusable after the first Flutter UI interaction.

Steps to Reproduce

We reproduced the issue after several different actions, including:

• opening and closing the Flutter Drawer;
• opening a partner detail;
• using the partner search;
• opening/closing Flutter UI elements over the map.

After returning to the map, the map remains visually displayed and the JavaScript/WebView is still running, but touch interactions are frozen.

Reproducible from Blank

• The steps to reproduce above start from a blank project.

Bug Report Code (Required)

IT4ojMmAx5dOseFK7aXqacEw+CQ4H0w/R5JEi8pBazwbfe+uB4kqevfOTERoYMSlY39cImH8kWoW0fzHuN7tC8YpAwedbYBnycxydgvKeHihM4y0FJWve395J+dmGGqb4cCN3BJDKtRfV3Bk70ymH+6+SnffGYy3OVQ8Da/LZO4=

Visual documentation

The problem is not specific to the Drawer: virtually any interaction that switches interaction between the WebView and Flutter UI can trigger it.

The same implementation works correctly on Android.

Important diagnostic test:
We instrumented the Custom Widget lifecycle with INIT/DISPOSE counters.

At initial map display:
INIT = 1
DISPOSE = 0

After opening and closing the Drawer:
INIT = 1
DISPOSE = 0

The map is nevertheless no longer touch-responsive.

Environment

Environment:
- FlutterFlow project
- Flutter version: 3.38.6
- iOS 26
- Custom Widget using WebView / HERE Maps JavaScript
- Android version works correctly
- Issue reproduced on iOS build/TestFlight
- App version: 3.0.0
- iOS build tested: 671

Additional Information

Important diagnostic test:
We instrumented the Custom Widget lifecycle with INIT/DISPOSE counters.

At initial map display:
INIT = 1
DISPOSE = 0

After opening and closing the Drawer:
INIT = 1
DISPOSE = 0

The map is nevertheless no longer touch-responsive.

This confirms that the Custom Widget/WebView is NOT being disposed or recreated when the issue occurs.

The WebView/JavaScript itself also remains active.

We are therefore suspecting an iOS PlatformView/WebView gesture handling issue rather than a HERE Maps or widget lifecycle issue.

This appears very similar to Flutter issues:

• flutter/flutter #175099
• flutter/flutter #176266
• flutter/flutter #191267

Issue #191267 is particularly relevant: it reports that a PlatformView/WebView can stop receiving touch events on iOS 26 while Flutter itself continues receiving the events.

A workaround mentioned there is:
FlutterPlatformViewGestureRecognizersBlockingPolicyDoNotBlockGesture

and a related fix is currently being worked on for webview_flutter_wkwebview (flutter/packages #12496).

Since FlutterFlow currently uses Flutter 3.38.6 for our project, we would like to know:

1. Is FlutterFlow aware of this remaining iOS 26 PlatformView/WebView gesture issue?
2. Is a Flutter/FlutterFlow update containing the upstream fix planned soon?
3. Is there a FlutterFlow-compatible workaround that can be applied without manually modifying the exported iOS project?
4. If not, would you recommend applying the native iOS gesture-recognizer blocking policy patch to the exported project for production?

This is currently blocking the release of our iOS application because the main map becomes unusable after the first Flutter UI interaction.