"Object reference not set to an instance of an object" on v21.2.10

[Julien Barach]

Hi,

This sample was working fine in 21.2.5 and now on 21.2.9 it throws an error :

<div>

    <SfComboBox TValue="string" TItem="string" DataSource="testSource" OnInput="change"

                AllowFiltering="true"

                EnableVirtualization="true"

                FilterType="Syncfusion.Blazor.DropDowns.FilterType.Contains"

                FloatLabelType="FloatLabelType.Auto"

                Autofill="true" />

</div>

@code {

    private List<string> testSource = new();

    private async Task change(Microsoft.AspNetCore.Components.ChangeEventArgs args)

    {

        testSource.Clear();

        await Task.Delay(1000);

        testSource = new List<string> { "1", "2", "3", "4" };

    }

}

Maybe it's a combination of parameters because if I remove some of them it seems to work. But again, it was working on 21.2.5.

[Julien Barach]

Update : still occurs on 21.2.10

[Julien Barach]

Hi,

Any fix planned on this topic ?

[Buvana Sathasivam]

Hi Julien,

We have checked your code with the sample and found the console error "Error: System.ArgumentNullException: Value cannot be null". We have already considered the reported issue "Combobox component not working properly when using EnableVirtualization as true" as a bug from our end, and the fix for the issue will be included after volume 2, which is expected on the second week of July 2023.

Now you can track the status of the reported issue through the feedback below,

Feedback Link:
https://www.syncfusion.com/feedback/44591/combobox-component-not-working-properly-when-use-enablevirtualization-as-true-with

Disclaimer: “Inclusion of this solution in the weekly release may change due to other factors including but not limited to QA checks and works reprioritization.”

Regards,

Buvana S

[Kokila Poovendran]

Hi Julien Barach,

We have included the fix for the issue "Combobox component not working properly when using EnableVirtualization as true“ 22.1.36”. Therefore, we recommend upgrading to our latest version to resolve the current issue.

Regards,

Kokila Poovendran.

[Julien Barach]

Hi,

I can confirm it's now working on 22.1.39.

Great work guys.

Regards,

JB

[Shereen Shajahan]

Hi Julien,

Glad to know your issue has been resolved. Please get back to us for assistance in the future.

Regards,

Shereen