We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy. (Last updated on: June 24, 2019).
Unfortunately, activation email could not send to your email. Please try again.
Syncfusion Feedback

[UWP] Crash with v17.2.0.51

Thread ID:

Created:

Updated:

Platform:

Replies:

147484 Sep 12,2019 07:37 AM UTC Sep 25,2019 08:39 AM UTC Xamarin.Forms 7
loading
Tags: SfNumericUpDown
Siggi
Asked On September 12, 2019 07:37 AM UTC

Hi, after updating SfNumericUpDown to v17.2.0.51 following Exception is thrown when the page should be shown.

XAML:
<xForms:SfNumericUpDown Grid.Column="1" Grid.Row="0" Value="{Binding CashReportVM.Count500_00}" ParsingMode="Decimal" Maximum="020" Minimum="0"
  MaximumDecimalDigits="0" FormatString="N0" SpinButtonAlignment="Left" HorizontalOptions="Start" WidthRequest="200" />

Exception:
"Object reference not set to an instance of an object."
"   at Syncfusion.SfNumericUpDown.XForms.SfNumericUpDown.ValidateMinimumValue(Object value, Object min, SfNumericUpDown numericUpDown, CultureInfo culture)\r\n   at Syncfusion.SfNumericUpDown.XForms.SfNumericUpDown.OnValueCallBackValueChanged(BindableObject bindable, Object value)\r\n   at Xamarin.Forms.BindableObject.SetValueCore(BindableProperty property, Object value, SetValueFlags attributes, SetValuePrivateFlags privateAttributes)\r\n   at Xamarin.Forms.BindingExpression.ApplyCore(Object sourceObject, BindableObject target, BindableProperty property, Boolean fromTarget)\r\n   at Xamarin.Forms.BindingExpression.Apply(Object sourceObject, BindableObject target, BindableProperty property)\r\n   at Xamarin.Forms.Binding.Apply(Object context, BindableObject bindObj, BindableProperty targetProperty, Boolean fromBindingContextChanged)\r\n   at Xamarin.Forms.BindableObject.SetBinding(BindableProperty targetProperty, BindingBase binding, Boolean fromStyle)\r\n   at Xamarin.Forms.Xaml.ApplyPropertiesVisitor.TrySetBinding(Object element, BindableProperty property, String localName, Object value, IXmlLineInfo lineInfo, Exception& exception)\r\n   at Xamarin.Forms.Xaml.ApplyPropertiesVisitor.SetPropertyValue(Object xamlelement, XmlName propertyName, Object value, Object rootElement, INode node, HydrationContext context, IXmlLineInfo lineInfo)\r\n   at Xamarin.Forms.Xaml.ApplyPropertiesVisitor.Visit(ElementNode node, INode parentNode)\r\n   at Xamarin.Forms.Xaml.ElementNode.Accept(IXamlNodeVisitor visitor, INode parentNode)\r\n   at Xamarin.Forms.Xaml.ElementNode.Accept(IXamlNodeVisitor visitor, INode parentNode)\r\n   at Xamarin.Forms.Xaml.ElementNode.Accept(IXamlNodeVisitor visitor, INode parentNode)\r\n   at Xamarin.Forms.Xaml.ElementNode.Accept(IXamlNodeVisitor visitor, INode parentNode)\r\n   at Xamarin.Forms.Xaml.ElementNode.Accept(IXamlNodeVisitor visitor, INode parentNode)\r\n   at Xamarin.Forms.Xaml.RootNode.Accept(IXamlNodeVisitor visitor, INode parentNode)\r\n   at Xamarin.Forms.Xaml.XamlLoader.Visit(RootNode rootnode, HydrationContext visitorContext, Boolean useDesignProperties)\r\n   at Xamarin.Forms.Xaml.XamlLoader.Load(Object view, String xaml, Boolean useDesignProperties)\r\n   at Xamarin.Forms.Xaml.XamlLoader.Load(Object view, Type callingType)\r\n   at Xamarin.Forms.Xaml.Extensions.LoadFromXaml[TXaml](TXaml view, Type callingType)\r\n   at FSM.Views.Cash.DayEndClosingPage.InitializeComponent() in C:\\Projekte\\FSM\\FSM\\obj\\x86\\Debug\\netstandard2.0\\Views\\Cash\\DayEndClosingPage.xaml.g.cs:line 21\r\n   at FSM.Views.Cash.DayEndClosingPage..ctor() in C:\\Projekte\\FSM\\FSM\\Views\\Cash\\DayEndClosingPage.xaml.cs:line 9\r\n   at Autofac.Core.Activators.Reflection.ConstructorParameterBinding.Instantiate()"

{System.Nullable`1[System.Double] ValidateMinimumValue(System.Object, System.Object, Syncfusion.SfNumericUpDown.XForms.SfNumericUpDown, System.Globalization.CultureInfo)}


Phil Holmes
Replied On September 13, 2019 04:44 AM UTC

Hi, after updating SfNumericUpDown to v17.2.0.51 following Exception is thrown when the page should be shown.

XAML:
<xForms:SfNumericUpDown Grid.Column="1" Grid.Row="0" Value="{Binding CashReportVM.Count500_00}" ParsingMode="Decimal" Maximum="020" Minimum="0"
  MaximumDecimalDigits="0" FormatString="N0" SpinButtonAlignment="Left" HorizontalOptions="Start" WidthRequest="200" />

Exception:
"Object reference not set to an instance of an object."
"   at Syncfusion.SfNumericUpDown.XForms.SfNumericUpDown.ValidateMinimumValue(Object value, Object min, SfNumericUpDown numericUpDown, CultureInfo culture)\r\n   at Syncfusion.SfNumericUpDown.XForms.SfNumericUpDown.OnValueCallBackValueChanged(BindableObject bindable, Object value)\r\n   at Xamarin.Forms.BindableObject.SetValueCore(BindableProperty property, Object value, SetValueFlags attributes, SetValuePrivateFlags privateAttributes)\r\n   at Xamarin.Forms.BindingExpression.ApplyCore(Object sourceObject, BindableObject target, BindableProperty property, Boolean fromTarget)\r\n   at Xamarin.Forms.BindingExpression.Apply(Object sourceObject, BindableObject target, BindableProperty property)\r\n   at Xamarin.Forms.Binding.Apply(Object context, BindableObject bindObj, BindableProperty targetProperty, Boolean fromBindingContextChanged)\r\n   at Xamarin.Forms.BindableObject.SetBinding(BindableProperty targetProperty, BindingBase binding, Boolean fromStyle)\r\n   at Xamarin.Forms.Xaml.ApplyPropertiesVisitor.TrySetBinding(Object element, BindableProperty property, String localName, Object value, IXmlLineInfo lineInfo, Exception& exception)\r\n   at Xamarin.Forms.Xaml.ApplyPropertiesVisitor.SetPropertyValue(Object xamlelement, XmlName propertyName, Object value, Object rootElement, INode node, HydrationContext context, IXmlLineInfo lineInfo)\r\n   at Xamarin.Forms.Xaml.ApplyPropertiesVisitor.Visit(ElementNode node, INode parentNode)\r\n   at Xamarin.Forms.Xaml.ElementNode.Accept(IXamlNodeVisitor visitor, INode parentNode)\r\n   at Xamarin.Forms.Xaml.ElementNode.Accept(IXamlNodeVisitor visitor, INode parentNode)\r\n   at Xamarin.Forms.Xaml.ElementNode.Accept(IXamlNodeVisitor visitor, INode parentNode)\r\n   at Xamarin.Forms.Xaml.ElementNode.Accept(IXamlNodeVisitor visitor, INode parentNode)\r\n   at Xamarin.Forms.Xaml.ElementNode.Accept(IXamlNodeVisitor visitor, INode parentNode)\r\n   at Xamarin.Forms.Xaml.RootNode.Accept(IXamlNodeVisitor visitor, INode parentNode)\r\n   at Xamarin.Forms.Xaml.XamlLoader.Visit(RootNode rootnode, HydrationContext visitorContext, Boolean useDesignProperties)\r\n   at Xamarin.Forms.Xaml.XamlLoader.Load(Object view, String xaml, Boolean useDesignProperties)\r\n   at Xamarin.Forms.Xaml.XamlLoader.Load(Object view, Type callingType)\r\n   at Xamarin.Forms.Xaml.Extensions.LoadFromXaml[TXaml](TXaml view, Type callingType)\r\n   at FSM.Views.Cash.DayEndClosingPage.InitializeComponent() in C:\\Projekte\\FSM\\FSM\\obj\\x86\\Debug\\netstandard2.0\\Views\\Cash\\DayEndClosingPage.xaml.g.cs:line 21\r\n   at FSM.Views.Cash.DayEndClosingPage..ctor() in C:\\Projekte\\FSM\\FSM\\Views\\Cash\\DayEndClosingPage.xaml.cs:line 9\r\n   at Autofac.Core.Activators.Reflection.ConstructorParameterBinding.Instantiate()"

{System.Nullable`1[System.Double] ValidateMinimumValue(System.Object, System.Object, Syncfusion.SfNumericUpDown.XForms.SfNumericUpDown, System.Globalization.CultureInfo)}


Same exception being thrown here also, on iOS. 

Was fine with v17.2.0.49!


Siggi
Replied On September 13, 2019 08:35 AM UTC

This really should be fixed before releasing 17.3.x.

Lakshmi Radha Krishnan [Syncfusion]
Replied On September 16, 2019 02:24 AM UTC


Hi Saggi,

 

We have fixed the reported issue and now ensuring all possible cases again. So, we will provide patch for this on or before Sep 17th, 2019. We appreciate your patience until then.

 

Regards,

Lakshmi R.

 


Rachel A [Syncfusion]
Replied On September 19, 2019 10:09 AM UTC

Hi Siggi, 
 
We deeply regret for the delay. 
 
We have already fixed the issue ensuring in all scenarios. We will provide the patch on 25th September 2019 in Volume 3 beta release version. 
 
We kindly appreciate your patience until then. 
 
Thanks, 
Rachel. 


Rachel A [Syncfusion]
Replied On September 24, 2019 12:05 PM UTC

Hi Siggi,


 
Thanks for your patience. 
 
As we promised earlier, we have completed the testing and generated the custom NuGet in the 17.3.0.9 version. Please check the reported issue after clearing the NuGet cache as mentioned in this link before referring the below NuGet and confirm us whether you are able to resolve the issue. 
 
 
The fix will be moved in the Volume 3 main release which is scheduled to be available on first week of October. Please let us know if you require any further clarifications.  
 
Thanks, 
Rachel. 


Siggi
Replied On September 25, 2019 08:12 AM UTC

Hi, just tested with 17.3.0.9, looks OK!

Rachel A [Syncfusion]
Replied On September 25, 2019 08:39 AM UTC

Hi Siggi, 
 
Thanks for the confirmation. 
 
Please let us know if you have any other concerns. 
 
Thanks, 
Rachel. 


CONFIRMATION

This post will be permanently deleted. Are you sure you want to continue?

Sorry, An error occured while processing your request. Please try again later.

Please sign in to access our forum

This page will automatically be redirected to the sign-in page in 10 seconds.

Warning Icon You are using an outdated version of Internet Explorer that may not display all features of this and other websites. Upgrade to Internet Explorer 8 or newer for a better experience.Close Icon

Live Chat Icon For mobile
Live Chat Icon