[Windows] Opening the flyout menu result in a binding failure

[Natriss]

Description

When you open and debug a .NET MAUI Windows app and open the navigation pane (flyout menu). It will give a binding failure.
Severity - Error
Count - 1
Data Context - Microsoft.UI.Xaml.Controls.SplitView
Binding Path - TemplateSettings.CompactPaneGridLength
Target - Microsoft.UI.Xaml.Media.Animation.SplineDoubleKeyFrame.Value
Target Type - Double
Description - Converter failed to convert value of type 'Windows.Foundation.IReference`1<Microsoft.UI.Xaml.GridLength>' to type 'Double'
File - null
Line - null
Project - null

Video.zonder.titel.Gemaakt.met.Clipchamp.mp4

Steps to Reproduce

1. Create a .NET MAUI app
2. Set Shell.FlyoutBehavior to Flyout
3. Debug the app and open the Flyout

Link to public reproduction project repository

No response

Version with bug

9.0.10 SR1

Is this a regression from previous behavior?

Not sure, did not test other versions

Last version that worked well

Unknown/Other

Affected platforms

Windows

Affected platform versions

10.0.19041.0

Did you find any workaround?

No response

Relevant log output

[kevinxufei]

This issue cannot be reproduced at Windows platform on the latest 17.13 Preview 1(9.0.10 & 9.0.0),but it's worth mentioning that I reproduced this problem on 8.0.100.

[Natriss]

I am using the latest preview of Visual Studio with the latest release build of .NET 9.

[Natriss]

https://github.com/[Natriss/MauiFlyoutIssue](https://github.com/Natriss/MauiFlyoutIssue)
Because the video is too big I've uploaded on my OneDrive so you can see it.
It's a full process from start to end.
Full video

[Tamilarasan-Paranthaman]

@Natriss, I tested this with the latest Visual Studio 17.13 Preview 2.1 version (9.0.21), and the issue is not reproducible. I have attached a video for your reference below. Could you please check your current version, update it to the latest version if you are using an older one, and check if the issue still persists?

WindowsFlyout.mp4

[Natriss]

@Tamilarasan-Paranthaman
With Visual Studio 17.12.3 and 17.13.0 Preview 2.1 + version 9.0.21, it's now fixed.
Now it also works with version 9.0.0, what I find weird, fixed is fixed :3