UWP- SfCombobox not working at all

[Emil]

I have a few problems on SfCombobox on UWP. the same code works on Android

1) it throws exception below

   at Windows.UI.Xaml.Controls.TextBox.put_SelectedText(String value)

   at Syncfusion.XForms.UWP.ComboBox.SfComboBox.OnComboBoxSourceChanged(DependencyObject obj, DependencyPropertyChangedEventArgs args)

   at Xamarin.Forms.Platform.UWP.TaskExtensions.<>c.b__2_1(Object e)

   at System.Threading.WinRTSynchronizationContextBase.Invoker.InvokeCore()

   at Windows.ApplicationModel.Core.UnhandledError.Propagate()

   at Microsoft.AppCenter.Utils.ApplicationLifecycleHelper.<.ctor>b__17_1(Object sender, UnhandledErrorDetectedEventArgs eventArgs)

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

EDIT: i have seen this topic is the same and I replied you there with a sample project. please check 

2) code below works on Android but not on UWP. as DisplayMemberPath, it shows type of the name attribute, not the actual value

   

   

in the viewmodel

     public List Languages { get; set; } = new List();

        private Language selectedLanguage;

        public Language SelectedLanguage

        {

            get { return selectedLanguage; }

            set

            {

                selectedLanguage = value;              

            }

        }

  public class Language 

    {

        public string name { get; set; }

        public string Image { get; set; }

    }

 

[Emil]

2) please try attached project on UWP, you can see that it is not displaying anything althoug on Android it works fine

Attachment: ComboBoxTrans_775f846c.zip

[Paul Anderson S]

Hi Emil, 

 

Thank you for using Syncfusion products. 

 

Query1: it throws exception below 

 

As we mentioned in the forum 138944 we are able to reproduce the issue and the fix will be included in our upcoming Volume 2 SP2 release which will be rolled out by the end of August 2018. 

 

Query2: you can see that it is not displaying anything althoug on Android it works fine 

 

We have checked the provided sample and the dropdown displayed as mentioned. On further analyzing we found that CahcedImageRenderer is not initialized in the UWP project which is needed if we use FFImageLoading. Please add the below code in the MainPage.xaml.cs file of UWP project. 

 

public MainPage() 

{ 

this.InitializeComponent(); 

CachedImageRenderer.Init(); 

LoadApplication(new ComboBoxTrans.App()); 

} 

 

Please let us know if you have any other concern. 

 

Regards, 

Paul Anderson 

[Emil]

Hi Paul,

Finally I could figure out the error but not the reason and solution :) I am attaching you a repro. There are 2 things triggering this error

Follow Steps;

1) Click "Go to MainPage" Button

2) in the new page there are 2 comboboxes, they are exactly the same but 1 is inside SfNavigationDrawer another is outside.

3) The one inside has binding not working, the one outside is fine. 

SfNavigation is the number 1 problem, number 2 problem is using a base class. please see the model object inherits from a base class. If I just move ID and name properties inside Employee object, both Comboxes are bound fine. 

More problem; SelectedItem throws exception on both Comboxes. 

 

All above scenario works fine on Android including SelectedItem.

 

Attachment: ComboBoxTrans_61aaac17.zip

[Paul Anderson S]

Hi Emil, 

 

We have checked the reported issue with “SfComboBox crash with Selecting an item and Binding issue with Base class properties” and we are able to reproduce the reported issue at our end in Xamarin.Forms UWP platform. We will fix the issues and the fix will be available in our Volume 2 SP2 release which will be rolled out by the end of August 2018. 

 

Regards, 

Paul Anderson 

[Emil]

is it possible that you can give me custom assemblies if it can be fixed earlier? thanks, Emil

[Paul Anderson S]

Hi Emil, 

  

Yes, We will create an DirectTrac incident shortly under your account and will update you the timeline for the custom assemblies in that. Please have further followups with that incident. 

  

Regards, 

Paul Anderson