Grid Pager has broken after Upgrading to 20.1.51

[Shelly Saunders]

After upgrading from 19.4.56 to 20.1.51 all Grid paging controls seem to have broken

The error stack is

Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100]

      Unhandled exception rendering component: Value cannot be null. (Parameter 'format')

System.ArgumentNullException: Value cannot be null. (Parameter 'format')

   at System.String.FormatHelper(IFormatProvider provider, String format, ParamsArray args)

   at System.String.Format(String format, Object arg0, Object arg1)

   at Syncfusion.Blazor.Grids.SfPager.BuildRenderTree(RenderTreeBuilder __builder)

   at Microsoft.AspNetCore.Components.ComponentBase.<.ctor>b__6_0(RenderTreeBuilder builder)

   at Microsoft.AspNetCore.Components.Rendering.ComponentState.RenderIntoBatch(RenderBatchBuilder batchBuilder, RenderFragment renderFragment, Exception& renderFragmentException)

[Renjith Singh Rajendran]

Hi Shelly,

Greetings from Syncfusion support.

We are not clear about the exact scenario you are facing the reported problem. We checked this by preparing a sample in 20.1.0.51 version, in which we could not reproduce the issue. We are attaching the sample for your reference.

Sample : https://www.syncfusion.com/downloads/support/directtrac/general/ze/ClientApp-481620408

We suspect that you might have missed adding the breaking changes while upgrading to our latest version. If so, then we suggest you to refer the below reference and ensure the below release notes with the application from your side.

https://blazor.syncfusion.com/documentation/release-notes/20.1.47?type=all#breaking-changes

If you are still facing difficulties, then the following details would be helpful for us to proceed further.

1. Share a simple issue reproducing sample or if possible reproduce the issue with the attached sample and share with us.
2. Share a video demo showing the replication of the problem you are facing.
3. Share the exact scenario you are facing this exception.

The provided information will help us analyze the problem, and provide you a solution as early as possible.

Regards,

Renjith R

[Shelly Saunders]

I definitely added the breaking changes because without them lots doesn't work. So its definitely the latest version because as soon as I rollback the nuget packages it all works again. 

It will be several days before I will have time to build something I can share with you though. I  simply do not have the time to debug this. I have had to rollback to previous version due to deadlines.  I would think the call stack is clear enough for you to go on, isn't it. 

[Renjith Singh Rajendran]

Hi Shelly,

As informed in our previous update, we not clear about the exact scenario you are facing this issue. We checked this but we could not face the reported exception when using paging in grid. So, we need the details requested from our previous update to further proceed on the reported issue and provide you a suggestion as early as possible.

Kindly get back to with us the requested details to proceed further.

Regards,

Renjith R

[Shelly Saunders]

Hi

I managed to find time to analyse this further. The bug on the pager control in v20 occurs when you have Syncfusion localization.

Using the steps described here:

Localization (Multi-Language) in Blazor components | Syncfusion

In the section Dynamically Set the Culture for Blazor WASM app, add the code suggested and the bug will appear.

Roll back your nugets to v19.4.0.56 and it will work again. 

I have created a zip file that reproduces the issue. 

Thank you

Shelly

Attachment: ClientApp__Pager_bug_with_localization_c48dbf03.zip

[Renjith Singh Rajendran]

Hi Shelly,

We checked this by adding the en-US resx file in the application. Now we could not reproduce the reported problem. We suggest you to add the corresponding resx files in your application to overcome the reported problem.

Resx GitHub link : https://github.com/syncfusion/blazor-locale/tree/master/src

We are also attaching a modified sample in this ticket. Please download and refer the attached sample.

Regards,

Renjith R

Attachment: ClientApp_6d713390.zip

[Shelly Saunders]

OK, explicitly adding this instead of relying on the default resx file has fixed the issue present in v20.1.0.51 and the Pager works again now

Thanks for your help

Shelly 

[Renjith Singh Rajendran]

Hi Shelly,

Thanks for your update. We are closing this ticket for now. Please create a new ticket if you need assistance on new queries.

Regards,

Renjith R