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. Image for the cookie policy date

[UWP] Crash (System.StackOverflowException) with v17.3.0.17

Hi again,

with the latest version (17.3.0.17) using the SfNumericUpDown control leads to an exception:
"An unhandled exception of type 'System.StackOverflowException' occurred in Syncfusion.SfInput.UWP.dll"
It just occurs with the following properties set:
SfNumericUpDown  ParsingMode="Decimal" Maximum="020" Minimum="0" MaximumDecimalDigits="0" FormatString="N0" SpinButtonAlignment="Left"

Without any properties set, the exception is not thrown.
I attached a project to reproduce the problem.
This bug kills my app during the most important usecase, please have a closer look what is causing this problem.

Regards.

Attachment: SchedulerTest20191009_ba1c59c3.zip

10 Replies

LR Lakshmi Radha Krishnan Syncfusion Team October 22, 2019 04:09 PM UTC

Hi Siggi,

Greetings from Syncfusion.

We are able to reproduce the issue at our end. We are checking this issue with high priority, we will update you the status on Oct 24, 2019.

Regards,
Lakshmi R.


RA Rachel A Syncfusion Team October 24, 2019 01:38 PM UTC

Hi Siggi, 
  
We can reproduce the issue (StackOverflowException thrown when setting ParsingMode as decimal in the SfNumericUpDown). We have confirmed this as an issue and logged bug report. We will include the fix in our upcoming weekly NuGet which is available on 29th October 2019. You can track the bug status from the below link. 
  
  
If you have any more specification/precise replication procedure or a scenario to be tested, you can add it as a comment in the portal link above. We appreciate your patience until then.  
 
Thanks, 
Rachel. 



RA Rachel A Syncfusion Team October 29, 2019 11:30 AM UTC

Hi Siggi, 
 
Sorry about the inconvenience. 
 
We have resolved the reported issue. As you are using weekly Nugget it is not possible to provide patch. 
 
We have not included this fix in 29th weekly NuGet and will move this fix in our upcoming Volume 3 SP1 release. So, we kindly appreciate your patience until then. 
 
Please let us know if you have any concerns. 
 
Thanks, 
Rachel. 



SI Siggi November 14, 2019 05:51 AM UTC

Hi,
could you explain why (if you have the fix for the problem already) you don't include it in the weekly fixes?
Regards


RA Rachel A Syncfusion Team November 14, 2019 06:05 AM UTC

Hi Siggi, 
 
Sorry for the delay. 
 
We have already included the fix in our Essential Studio Volume 3 SP 1 2019 (v17.3.0.26)  and is available for download under the following link. 
 
 
We thank you for your support and appreciate your patience in waiting for this release. Please get in touch with us if you would require any further assistance. 
 
Thanks, 
Rachel. 



SI Siggi November 14, 2019 02:32 PM UTC

Ok, thank you for that info.
It would be very helpful to include all bugfixes in the release notes, in that case it would have been clearly that the bug is already fixed.
Regards


RA Rachel A Syncfusion Team November 15, 2019 05:17 AM UTC

Hi Siggi, 
 
We have mentioned the fix in release notes link. 
 
 
Thanks, 
Rachel. 



SI Siggi November 16, 2019 08:18 AM UTC

Hi Rachel,
as I'm using Xamarin.Forms, I haven't looked in the UWP release notes.
If possible it would be great to include the fixes also in the Xamarin release notes.
Regards


RA Rachel A Syncfusion Team November 18, 2019 08:48 AM UTC

Hi Siggi, 
 
We will mention the fix in Xamarin Forms release notes and will update you once it is reflected in live.  
 
Thanks, 
Rachel. 



RA Rachel A Syncfusion Team November 19, 2019 11:42 AM UTC

Hi Siggi, 
 
We have included the fix in Xamarin Forms release notes, check the link below. 
 
 
Thanks, 
Rachel.  


Loader.
Live Chat Icon For mobile
Up arrow icon