Skip to content
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

[Bug] [UWP] Template Disappears when Command Parameter Binding Set #1995

Closed
djrpascu opened this issue Jan 12, 2020 · 2 comments
Closed

[Bug] [UWP] Template Disappears when Command Parameter Binding Set #1995

djrpascu opened this issue Jan 12, 2020 · 2 comments

Comments

@djrpascu
Copy link

Description

I have a Listview with simple DataTemplate selector which presents one of either two templates. Once the CommandParameter Binding is defined to the current object ({Binding} or {Binding .}), the entire view for that template goes blank on UWP. Therefore, I'm not allowed to call the command with the current object. This works as expected when deploying out to iOS.

Note: I originally submitted this issue in the XF Github #8918. @PureWeen discovered that it works as expected when using Xamarin.Forms.Command. So, perhaps issue is specific to Prism DelegateCommand?

Steps to Reproduce

Sample project here https://github.com/djrpascu/XFGithub

Expected Behavior

Listview template displays contents properly and I'm able to pass the object into my command via CommandParameter.

Actual Behavior

Listview template goes blank.

Basic Information

  • Version with issue: 4.4.0.991265

  • Last known good version: N/A

  • IDE: VS Enterprise 2019 16.4.1

  • Platform Target Frameworks:

    • iOS: 13
    • Android: N/A
    • UWP: 16299
  • Android Support Library Version: N/A

  • Nuget Packages:
    XF 4.4.0.991265
    Prims.Unity.Forms 7.2.0.1422
    NETStandard.Library 2.0.3

  • Affected Devices:
    Windows 10 Desktop

Screenshots

Reproduction Link

https://github.com/djrpascu/XFGithub

@dansiegel
Copy link
Member

The InvalidCastException is by design. You are getting the wrong value into the CommandParameter. As I mentioned on your original issue this has to be a bug in Xamarin.Forms.

@lock
Copy link

lock bot commented Jan 28, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants