-
Notifications
You must be signed in to change notification settings - Fork 675
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
Exception thrown after closing window with flyout that contains a color picker #7239
Comments
Just to give an update. Recently updated to Windows 11 (21H2) Build: 22000.832, and after testing this again with both Windows App SDK 1.1.2 and 1.1.3, it seems that this issue isn't present anymore. Last time I checked on Windows 10 was with Windows App SDK 1.1.2 and the issue was still there. |
After the drag & drop issues seem to be fixed in App SDK v1.2.0-preview1 I now see colorpicker triggered crashes as described in this ticket. This is a regression of App SDK v1.1.x versions as it was fine for all App SDK v1.0.x versions. Currently, this is a blocker for us for internal testing of the application. @codendone, @ojhad As the issue looks suspiciously similar to #7260 I've tried the workaround as proposed by dotnet/maui#7317 (comment). As my code is WinRT C++ based, I used the following code fragment.
Unfortunately, it doesn't solve the crashes that I observe. Is it correct that the tickets are related? Or do I miss something with the workaround? I hope that we get soon a fix for this issue so that at least we do not suffer anymore from regression of v1.1.x. It would allow us to step finally from App SDK v.1.0.x to something newer. Any fix or workaround would be highly appreciated. |
@codendone The issue is still visible with App SDK 1.2.221116.1. |
This issue is still a regression of all 1.x and 2.x App SDK releases for the Windows 10 platform. I've also tested the latest v1.2.2 release with the same results. On Windows 11 platforms the crash cannot be observed (using the same test code). It currently blocks us from finally upgrading from the outdated 1.0.4 release to something up-to-date without the need to design our own color picker. |
@jschwizer99 Thanks for your patience. We have a fix for this issue and will endeavor to include it in the next 1.2 servicing release. |
@Scottj1s Many thanks for this positive news! I'm looking forward to testing it. |
And thanks @dkreho1 for reporting this issue. The fix will be available soon in the next servicing release, 1.2.3. |
Fix is now available: https://www.nuget.org/packages/Microsoft.WindowsAppSDK/1.2.230118.102 |
Describe the bug
Window defined with the following C++ code:
If I click on the button to open the flyout everything works fine but when I close the window the following exception is thrown:
If I don't open the flyout the exception isn't thrown. Same thing happens if I use XAML to define the same window in MainWindow.xaml. I have tried the same with some other controls, in particular with TextBlock, DatePicker and TimePicker, and the window closes fine without this exception. Also reverted back to Microsoft.WindowsAppSDK 1.0.3 and no exception gets thrown so I'm assuming the issue is with Microsoft.WindowsAppSDK 1.1.0.
Steps to reproduce the bug
Expected behavior
Window to close without any exceptions.
Screenshots
NuGet package version
No response
Windows app type
Device form factor
No response
Windows version
Windows 10 (21H2): Build 19044
Additional context
Using Microsoft.WindowsAppSDK 1.1.0
The text was updated successfully, but these errors were encountered: