-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ComposeWindow is shown before the first frame is rendered #3492
ComposeWindow is shown before the first frame is rendered #3492
Comments
Hmm, could have to do with the navigation lib you are using? |
I don't think so, navigation is being made with NavigationStack on iOS side (no 3rd party). |
We will add explicit wait for the first rendered frame to avoid this. I'll link related PR when it's done. |
Fixed in PR |
@elijah-semyonov not deployed yet right? |
Not yet, will be in next version. |
FYI, still seeing this in 1.5.1. Can we add an option to set the background color? I don't think you'll ever be ever to guarantee that Compose goes through a whole draw pass before iOS does. |
Yup tested again with:
And I can still see the white background. |
@GuilhE |
Yes of course, check it here https://github.com/GuilhE/Expressus |
My bad, the fix is not live yet. Will be there in 1.5.10. |
I can confirm that |
Updated also my sample if anyone want's a fast test candidate 😉 |
I'm hitting this problem avoiding SwiftUI using normal UIViewController classes. I even tried to force the background of the views to black before pushing them with pseudo code like this:
But that didn't work at all. Version |
1.5.10-beta02 has fixed the issue for us. I didn’t try beta01 though so not sure if that contains the fix. |
1.5.10-beta01 and beta02 fixed for me, no need for backgrounds hack, which btw, never managed to make it work 😅 |
Describe the bug
White flickering when presenting/pushing ComposeWindow
Affected platforms
Versions
Latest master
Screen.Recording.2023-08-14.at.14.18.47.mov
Meta
Reported by Guilherme Delgado
The text was updated successfully, but these errors were encountered: