Grzegorz Miszewski

Exactly the same issue here... I build app and have crash due to this error. But after clean it works once and build again - crash... I think it's related...

Looking at material docs It looks like this should be supported. https://material.io/components/sheets-bottom#expanding-bottom-sheet There are times where it's applicable to animate BottomSheet to full screen and let user swipe it down....

I know that I can do that this way, it's just cumbersome, and in Kotlin it prevents for use of {}

We do the same thing, it would be great feature

Exactly, is it?:)

I have a question regarding this. I wonder why app needs to display full screen CustomTab at first place? This is really ugly UX experience.

I've encountered this issue. And due to that I can't handle ExoPlayer release() correctly in screen, when app get's paused. Any info about bugfix here?

We encountered the same issue. When our website detects mobile Safari we swap the input and put it on top of the page. Of course, this was a workaround, but...

@darshankawar you don't see this error on this website. https://api.de-team.com/flutter/ ? For me I have repro on Pixel 6 Pro using latest Android and Chrome

Hi, More and more of our clients write about having this issue. Is there any chance to boost the priority of this bug?