SyncFusion Blazor Schedular spinner keeps spinning.

I was using SyncFusion version 18.0.1.59. When I updated the version to 18.0.2.59, the Schedular loads but the spinner never stops and does not let the user do anything. I have attached a screenshot.

3 Replies 1 reply marked as answer

AK Alagumeena Kalaiselvan Syncfusion Team October 1, 2020 02:06 PM UTC

Hi Bibek, 

Thanks for contacting Syncfusion support! 

We have checked your reported issue “Scheduler spinner keeps loading” with specified package version 18.0.2.59 but we regret to inform you that issue could not be replicated at our end. Also we have prepared a  sample along video demo for your reference which can be downloaded from the below link. 

Please try to share the below details to proceed further 
  • Share the Scheduler rendering sample code if possible
  • Replicate your issue with shared sample
  • Share the issue replicating scenario

Regards 
Alagumeena.K 


Marked as answer

TC Tom Corrigan October 2, 2020 12:44 AM UTC

See the forum article AppointmentData values not showed on Scheduler Syncfusion Blazor 18..0.56


BS Balasubramanian Sattanathan Syncfusion Team October 2, 2020 09:12 AM UTC

Hi Tom Corrigan, 

Thanks for the update. 

We have validated your reported scenario “SyncFusion Blazor Schedular spinner keeps spinning” at our side and we suspect that you have rendered the more number of appointments in the Scheduler, it could be the cause for the reported problem. And we let you know that the Blazor application uses SignalR connection to manage communication between the server and client. By default, SingalR limits the buffer size to 32 KB. So increase the buffer size of the blazor application to render large number of appointments. To increase the connection buffer size, set the MaximumReceiveMessageSize property shown below in the startup.cs file within (ConfigureServices) method. And we would suggest you to upgrade our latest version and check it at your side whether the problem has occurred or not. 

services.AddServerSideBlazor().AddHubOptions(o => { o.MaximumReceiveMessageSize = 102400000; }); 


Kindly try the above solution and let us know if this is helpful. 

Regards, 
Balasubramanian S 


Loader.
Up arrow icon