Calendar not calculating correctly dates

[David Perera]

Hello,

My SfCalendar on iOS gives me wrong dates (e.g. it says that 14/09/2018 is Saturday and is Friday). On Android it works perfectly.

I have the custom dlls you gave me on:

https://www.syncfusion.com/support/directtrac/incidents/191495

Regards.

[Vigneshkumar Ramasamy]

Hi David Perera,

Thank you for contacting Syncfusion Support.

Based on the provided information, we have checked the issue with ”SfCalendar displays wrong days on iOS” and it is working fine from our side. We have checked in the scenario of by setting FirstDayofWeek, MinDate and MaxDate and Changing the Time Zone. Can you please upgrade to our current version 2018 Volume 3 Beta v16.3.0.17, and is available for download under the following link:

https://www.syncfusion.com/forums/139764/essential-studio-2018-volume-3-beta-release-v16-3-0-17-is-available-for-download

We have prepared the sample with already provided custom assemblies. Please find the sample from the below link,

Sample Link: http://www.syncfusion.com/downloads/support/forum/139845/ze/Sample-127077009.zip

If the given sample also doesn’t meet your requirement, could you please modify the provided sample along with its reproducing procedure? It will be helpful for us to analyze on your requirement and provide you a possible solution.

Regards,
Vigneshkumar R  

[David Perera]

Hi, I have downloaded from Nuget your packages of 2018 Volume 3 Beta v16.3.0.17, and I have downloaded the beta version from your link, logged correctly, and copy the new key to my code.

The problem is that it pop-ups a syncfusion message that says that the key is invalid... (I don't know if it is since all the components are not in the latest version and the key is not valid for previous versions, but I think some component give me problems updating and I did not update because of that)

Regards.

[Vigneshkumar Ramasamy]

Hi David Perera, 

 

We suspect that, you may be using the v16.2.0.x license key for v16.3.0.17 assemblies in your project. Syncfusion license keys are version specific. Please follow the below knowledge base to generate the v16.3.0.17 license key.  

  

https://www.syncfusion.com/kb/8976    

 

Regards 

Vigneshkumar R 

 

[David Perera]

Hello,

I have generated the key for the 16.3.0.17 beta version, and I get a version mismatch error. My Syncfusion.Licensing package is on 16.3.0.17-beta, abd the calendar dlls also, but I do have older dlls for the rest of the application. For example for Syncfusion.Xamarin.Core I have 16.2.0.46. Is that the issue?? (because I do not want to update everything)

Thanks,

Regards.

[Vigneshkumar Ramasamy]

Hi David Perera, 

 

We recommending to keep the single version of Syncfusion assemblies in an application. Yes, the corresponding Syncfusion version license key should be registered in your application. If you want to keep the both Syncfusion both versions, then you must register the both versions license key in your Xamarin application as below. 

   

public App()  

{  

               //Register Syncfusion license  

               Syncfusion.Licensing.SyncfusionLicenseProvider.RegisterLicense("YOUR v16.2.0.46 LICENSE KEY");    

               Syncfusion.Licensing.SyncfusionLicenseProvider.RegisterLicense("YOUR v16.3.0.17 LICENSE KEY");    

  

                 

               InitializeComponent();  

                 

               MainPage = new App1.MainPage();  

}  

 

 

 

Documentation: https://help.syncfusion.com/common/essential-studio/licensing/license-key#xamarinforms  

 

Regards,  

Vigneshkumar R 

[David Perera]

Thanks, that works.

I guess this only happens because I have a beta version right? (or if I have N syncfusion versions I need to have N licenses)

Regards.

[Vigneshkumar Ramasamy]

 

Hi David Perera,  

 

No, Syncfusion introducing the new licensing system from v16.2.0.41. So, you can to generate the license key for v16.2.0.41 and later and register the corresponding version license key in your application.  

  

If you are using N number of Syncfusion version in your single application, then you have to register the all the version license key. But best practice, we need to keep all the reference assemblies are in single version.   

  

Regards,  

Vigneshkumar R