Menu sample sometimes "Render" call fails.

[Rosuavio]

Describe the bug

When opening up the Menu sample the render call at Microsoft.Toolkit.Uwp.SampleApp\Pages\SampleController.xaml.cs 506 fails the first time and works after waiting and opening up the Menu sample a second time. The text that is being rendered is the same on the times that it fails as the times that it succeeds.

failed.txt

This error get logged.
Exception thrown: 'Windows.UI.Xaml.Markup.XamlParseException' in Microsoft.Toolkit.Uwp.SampleApp.exe WinRT information: Unknown parser error: Scanner 2148734242. [Line: 205 Position: 41]

Broke in the split controls merge.

• Is this bug a regression in the toolkit? If so, what toolkit version did you last see it work:

Steps to Reproduce

• Can this be reproduced in the Sample App? (Either in a sample as-is or with new XAML pasted in the editor.) If so, please provide custom XAML or steps to reproduce. If not, let us know why it can't be reproduced (e.g. more complex setup, environment, dependencies, etc...)

Steps to reproduce the behavior:

1. Open Menu sample on sample app.
2. Menu sample does not load.

Expected behavior

A clear and concise description of what you expected to happen.

Screenshots

If applicable, add screenshots to help explain your problem.

Environment

NuGet Package(s): 

Package Version(s): 

Windows 10 Build Number:
- [ ] Fall Creators Update (16299)
- [ ] April 2018 Update (17134)
- [ ] October 2018 Update (17763)
- [ ] May 2019 Update (18362)
- [ ] May 2020 Update (19041)
- [ ] Insider Build (build number: )

App min and target version:
- [ ] Fall Creators Update (16299)
- [ ] April 2018 Update (17134)
- [ ] October 2018 Update (17763)
- [ ] May 2019 Update (18362)
- [ ] May 2020 Update (19041)
- [ ] Insider Build (xxxxx)

Device form factor:
- [ ] Desktop
- [ ] Xbox
- [ ] Surface Hub
- [ ] IoT

Visual Studio 
- [ ] 2017 (version: )
- [ ] 2019 (version: ) 
- [ ] 2019 Preview (version: )

Additional context

Add any other context about the problem here.

Hello RosarioPulella, thank you for opening an issue with us!

I have automatically added a "needs triage" label to help get things started. Our team will analyze and investigate the issue, and escalate it to the relevant team if possible. Other community members may also look into the issue and provide feedback 🙌

[michael-hawker]

Hmm, wonder if we missed updating something in the XAML. Very bizarre. Wonder if we try pulling the NuGet package and copying the sample XAML into an app if we'd see the same problem?

Does the app get taken down or does it just not work the first time?

[Rosuavio]

When trying to make the sample code work in a project I would get this error 1>C:\Program Files (x86)\Windows Kits\10\bin\10.0.19041.0\XamlCompiler\Microsoft.Windows.UI.Xaml.Common.targets(312,5): Xaml Internal Error error WMC9999: This Member 'Resources' has more than one item, use the Items property

Jumping to the error line did not help at all. But InteliSense highlighted <Style TargetType="MenuFlyoutItem"> and I had to move that whole block inside the ResourceDictionary and then it worked fine.

[Rosuavio]

The same change in the sample app did not seem to fix it.

[Rosuavio]

Does the app get taken down or does it just not work the first time?

The sample just does not render the first time.

[michael-hawker]

Yeah, this is really weird. Fiddling with it, I can eventually get it to work with the same code that was there.

I noticed a similar issue in ListDetailsView with one of the Styles...

I feel like the only Sample App stuff that has changed was in #3648? But can't see how that'd be an issue here. We could try doing more comparisons between 6.1 and now. Though this really seems like some weird timing issue?

[michael-hawker]

@RosarioPulella did you test in Release mode too without the Debugger attached or only in Debug w/ Debugger? Wondering if it behaves the same way or not?

[Rosuavio]

So currently I am having issues building in release. But after some small changes to get it to build the menu sample does open up on the first try. I don't know how or why but not an issue in Release 🤔. I can still investigate the commits and see where it was introduced.