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
Current Solution:
The latest master channel flutter(3.1.0 pre) already merge the improved PR, which improved a lot but bug still here:(
I am testing the result of later version of Android SDK level(24+)
But also considering downgrade to flutter 2.10.5, I would try my best to avoid though
PS: this bug does not exist in iOS.
The text was updated successfully, but these errors were encountered:
I don't know this project, but I found this issue by looking at issues related to flutter_unity_widget.
The flicker is actually the page transition failing to render properly.
If you add a custom transition for this page where the duration is 0, you won't get the flicker.
It won't happen in flutter 2.10.5 because the plugin uses a different type of platformview by default in Flutter < 3.0
This was disabled for Flutter 3.0 because of the issues you linked.
I don't know this project, but I found this issue by looking at issues related to flutter_unity_widget.
The flicker is actually the page transition failing to render properly. If you add a custom transition for this page where the duration is 0, you won't get the flicker.
It won't happen in flutter 2.10.5 because the plugin uses a different type of platformview by default in Flutter < 3.0 This was disabled for Flutter 3.0 because of the issues you linked.
Uh oh!
There was an error while loading. Please reload this page.
A P4 level bug causing
PlatformView
on theUnityWidget
layout and rendering problemsFull detail plz look up flutter/flutter#103630
The main reason issue: flutter/engine#33599
Current Solution:
The latest master channel flutter(3.1.0 pre) already merge the improved PR, which improved a lot but bug still here:(
I am testing the result of later version of Android SDK level(24+)
But also considering downgrade to flutter 2.10.5, I would try my best to avoid though
PS: this bug does not exist in iOS.
The text was updated successfully, but these errors were encountered: