Closed bcaceiro closed 1 year ago
We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.
Hi @bcaceiro. We have added the "s/try-latest-version" label to this issue, which indicates that we'd like you to try and reproduce this issue on the latest available public version. This can happen because we think that this issue was fixed in a version that has just been released, or the information provided by you indicates that you might be working with an older version.
You can install the latest version by installing the latest Visual Studio (Preview) with the .NET MAUI workload installed. If the issue still persists, please let us know with any additional details and ideally a reproduction project provided through a GitHub repository.
This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.
Verified this issue with Visual Studio Enterprise 17.7.0 Preview 1.0. Not repro on Android platform with sample project. /MAUIMainPageBug
Description
When swapping the MainPage ( and yes, not using Navigation / Shell), there is a black screen flicker always visible. This did not happen in Xamarin.Forms. The more complex layout in the page, this black screen increases its duration. For the sake of demonstration, I attach a simple project, with a simple page with 1 button, but in real case, there are pages with way more visual complexity.
See video -> https://streamable.com/acsmth
Steps to Reproduce
Link to public reproduction project repository
https://github.com/bcaceiro/MAUIMainPageBug
Version with bug
7.0 (current)
Last version that worked well
Unknown/Other
Affected platforms
Android
Affected platform versions
Android API30, 31, 32
Did you find any workaround?
No response
Relevant log output