Closed PratzelBoy closed 2 months ago
Hey there, thanks for the report! I have trouble reproducing this. I loaded the sample app, made the change you suggested and run it on a Pixel 5 emulator with API 33 and I can rotate and open and close the flyout as much as I want but nothing seems to happen. Is it specific to tablets? Is there anything else I'm missing?
Hi @PratzelBoy. We have added the "s/needs-info" label to this issue, which indicates that we have an open question for you before we can take further action. 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.
@jfversluis yes, it seems to be reproducible only on tablets. The emulator I used has this config.ini:
disk.dataPartition.size=6442450944 fastboot.chosenSnapshotFile= fastboot.forceChosenSnapshotBoot=no fastboot.forceColdBoot=no fastboot.forceFastBoot=yes hw.accelerometer=yes hw.arc=no hw.audioInput=yes hw.battery=yes hw.camera.back=virtualscene hw.camera.front=emulated hw.cpu.ncore=4 hw.dPad=no hw.gps=no hw.gpu.mode=auto hw.initialOrientation=landscape hw.keyboard=yes hw.lcd.density=320 hw.lcd.height=1600 hw.lcd.width=2560 hw.mainKeys=no hw.ramSize=2048 hw.sdCard=yes hw.sensors.orientation=yes hw.sensors.proximity=no hw.trackBall=no runtime.network.latency=none runtime.network.speed=full sdcard.size=512M skin.dynamic=yes skin.name=pixel_tablet skin.path=[UNDISCLOSED] vm.heapSize=192 AvdId=Pixel_Tablet_API_32 PlayStore.enabled=false abi.type=x86_64 avd.ini.displayname=Pixel Tablet API 32 hw.cpu.arch=x86_64 hw.device.hash2=MD5:3eb16c85159ad6e1cbb3263194d1a735 hw.device.manufacturer=Google hw.device.name=pixel_tablet hw.gpu.enabled=yes image.sysdir.1=system-images\android-32\google_apis\x86_64\ showDeviceFrame=yes tag.display=Google APIs tag.id=google_apis
With a tablet I see it indeed, interesting!
Possibly related #18161
We've added this issue to our backlog, and we will work to address it as time and resources allow. If you have any additional information or questions about this issue, please leave a comment. For additional info about issue management, please read our Triage Process.
Same here. This only happens when the FlyoutPage flyout is presented in portrait mode. When it's always open, for example in landscape mode or the flyout is closed, the app won't crash.
@jfversluis Is this something that can get priority? Because this prevents the use of the FlyoutPage on Android devices.
@imuller unfortunately I'm not in charge of priorities, there is a lot involved to determine those. Unfortunately this didn't bubble up yet it seems. If this is really something that is blocking you you might consider giving us a hand an pull down the .NET MAUI repository and have a look yourself or even provide a PR!
Another regression. MS should consider continuing support on Xamarin as long as such basic features do not work properly in MAUI.
Not fixed. Please see https://github.com/dotnet/maui/issues/18161
Why is this issue closed? I see no open issue addressing it. The crash is rather easy to reproduce with latest MAUI. The workaround by @guyvaio sadly didn't fix it for us either..
Description
On Android, using your sample FlyoutPage project, the application crashes on a simple orientation change. https://github.com/dotnet/maui/assets/140050432/46b96486-f2b3-4d0e-82fa-21dd4a60ca6b
The command 'dotnet workload list' give the following output on my setup:
Welcome to .NET 8.0!
SDK Version: 8.0.200
Installed Workload Id Manifest Version Installation Source
maui-windows 8.0.6/8.0.100 VS 17.10.34607.79, VS 17.9.34616.47 maccatalyst 17.2.8022/8.0.100 VS 17.10.34607.79, VS 17.9.34616.47 ios 17.2.8022/8.0.100 VS 17.10.34607.79, VS 17.9.34616.47 android 34.0.79/8.0.100 VS 17.10.34607.79, VS 17.9.34616.47 aspire 8.0.0-preview.3.24105.21/8.0.100 VS 17.10.34607.79
Steps to Reproduce
Link to public reproduction project repository
https://github.com/dotnet/maui-samples/tree/main/8.0/Navigation/FlyoutPageSample
Version with bug
Unknown/Other
Is this a regression from previous behavior?
Not sure, did not test other versions
Last version that worked well
Unknown/Other
Affected platforms
Android
Affected platform versions
Android API 32, Android API 34...
Did you find any workaround?
No response
Relevant log output