A uikitview is below B uikitview, but A uikitview is refreshed, so that B uikitview cannot respond to the click event

[chikang]

step：
1: Click the "Click Me" button, and a red B_uikitView native control pops up.
2: Then wait 5 seconds and the A_uikitView native control will show up,
3: At this point, the red B_uikitView native button is unresponsive

red button dont click!!!!!! why!!!!

my demo

UIKitViewDemo.zip

[chikang]

[chikang]

problem ： When the red view comes out, the green button cannot be clicked

[exaby73]

I can reproduce this issue with the steps above. This may be a duplicate of #37579 but I cannot be certain of it. Labeling for further insights from the team

[chikang]

This doesn't look like #37579，My problem is inevitable, and a demo is provided，so，how to solve this problem？

[exaby73]

@chikang The team has yet to look at this issue and prioritize it. Unfortunately, the only thing to do is wait for that to happen

[chikang]

@chikang The team has yet to look at this issue and prioritize it. Unfortunately, the only thing to do is wait for that to happen

Well, I hope to hear from you soon @exaby73

[hellohuanlin]

Did some initial investigation. From the debug view it looks like the green box is on top of the button:

However, in the actual screen, the red button is not covered by the green box. So my guess is that flutter's platform view actually crop out the central area of green box so that it doesn't cover the red button.

@cyanglaz probably has more insight?

[cyanglaz]

Is the green uikitview intended to be below the red uikitview?

[hellohuanlin]

@cyanglaz I think so, the red button is displayed using "showDialog" (which i assume should be the highest z order?):

FloatingActionButton(
    onPressed: () {
      showDialog(
          context: context,
          builder: (context) {
            return Container(
              width: 300,
              height: 300,
              child: const UiKitView(
                viewType: 'B_uikitView',
                creationParamsCodec: StandardMessageCodec(),
              ),
            );
          });
    },
    child: Text(
      '点我',
      style: TextStyle(color: Colors.white, fontSize: 13),
    )),
],

[cyanglaz]

So it might be a issue with zIndex of PlatformView when displaying in a dialog?

I think the click event worked as expected. The green view suppose to cover the red view, so the red view should not be handle touch events. The issue is the green view is displaying at the wrong zIndex.

[chikang]

So it might be a issue with zIndex of PlatformView when displaying in a dialog?

I think the click event worked as expected. The green view suppose to cover the red view, so the red view should not be handle touch events. The issue is the green view is displaying at the wrong zIndex.

I also think it has something to do with zIndex, but how to solve it, I don't know

[chikang]

How can red view get click events？

[chikang]

Is there a widget or API to solve this problem？

[KenwayDev]

I had the same problem:
The view in flutter is presented as half screen black at the top of the screen, and the view is a WKWebview. But as you can see from the Xcode view hierarchy, half a screen of WKWebview is blocked by another UIView. The event in WKWebview is now unclickable。

@exaby73

[hellohuanlin]

Is there any progress?

Hi, I got some good leads on this issue, but later got pulled into another issue so I paused it. Will resume after that issue is resolved.

[hellohuanlin]

@chikang yep, from where i left off, it should be solvable if im not mistaken.

[jmagman]

@chikang please refer to https://github.com/flutter/flutter/wiki/Issue-hygiene#do-not-add-me-too-or-same-or-is-there-an-update-comments-to-bugs. When there are update to report on this issue, it will be commented on and/or closed.

[github-actions]

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 -v and a minimal reproduction of the issue.