ListvewExtensionsPage Command prop not found

[Rosuavio]

Describe the bug

A clear and concise description of what the bug is.
After building the sample app locally (Debug|x64) when opening the ListViewExtensions sample the sample app crashes with the error

Windows.UI.Xaml.Markup.XamlParseException
  HResult=0x802B000A
  Message=The text associated with this error code could not be found.

Cannot deserialize XBF metadata property list as 'Command' was not found in type 'Microsoft.Toolkit.Uwp.UI.ListViewExtensions'. [Line: 0 Position: 0]
  Source=<Cannot evaluate the exception source>
  StackTrace:
<Cannot evaluate the exception stack trace>

• 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. In the sample app
2. Open the ListViewExensionsPage sample
3. See error

Expected behavior

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

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 🙌

[Rosuavio]

@deanchalk and @Sergio0694, maybe you can us investigate whats going on here.

[Sergio0694]

Mh, this is odd, the ListViewExtensions sample page is working just fine for me with the app from the Store. Clicking on items also works correctly, invoking the command that's bound through the extension. Were you using the Store version or a local build? If it was a local build, this was with .NET Native in Release mode I assume? 🤔

[Rosuavio]

Were you using the Store version or a local build? If it was a local build, this was with .NET Native in Release mode I assume? 🤔

I should have mentioned, Local build, Debug|x64

[michael-hawker]

This seems similar to the issue we were seeing before with Menu as well. Which all work fine in Release mode I believe in the store app. So this may be an SDK issue?

We probably need to construct a small repo with XamlReader in an app to open an issue on WinUI?

[IsmailHassani]

I have the same issue.
As soon i use an ICommand or Attached property with iCommand in a ListView you get this error.
I posted this issue on Discord post a while ago, but it seems this issue was causing the problem initially why i couldn't upgrade to version 7.0.2.
If i go back to version 6.1.1 the issue is gone.

These are the errors i get:

Windows.UI.Xaml.Markup.XamlParseException: The text associated with this error code could not be found. Cannot deserialize XBF metadata property list as 'DoubleTappedCommand' was not found in type 'ISynergy.Framework.UI.Controls.ListViewAttached'

and

Windows.UI.Xaml.Markup.XamlParseException: The text associated with this error code could not be found. Cannot deserialize XBF metadata property list as 'Command' was not found in type 'Microsoft.Xaml.Interactions.Core.InvokeCommandAction'.

[michael-hawker]

Wondering if this is related or the same as microsoft/microsoft-ui-xaml#4614 as we did take the dependency on WinUI 2.5 at that time.

We probably need a small sample with just our Toolkit ICommand ListViewExtension helper in an app, see if it works. Then add WinUI 2.5 dependency and resources in and see if it breaks...

@RosarioPulella once you're done with the UI Tests, want to see if you can test this out in a file new UWP app and see what happens? Then if we have a repro showing its at least related to WinUI, we can attach to the above issue and raise with the WinUI team for 2.6.