Newtonsoft.Json error with Toast

Hi,
I get this error when I try to show a Toast.

Newtonsoft.Json.JsonSerializationException: Error converting value "{"easing":"ease"}" to type 'Syncfusion.Blazor.Notifications.ToastAnimationSettingsShow'. Path 'show', line 1, position 31. ---> System.ArgumentException: Could not cast or convert from System.String to Syncfusion.Blazor.Notifications.ToastAnimationSettingsShow.

Version: 18.1.0.55
Platform: WebAssembly (client side)

    <SfToast @ref="ToastObj" 
             Title="Saved" ShowCloseButton="true" 
             CssClass="e-toast-success"
             TimeOut=5000 Icon="e-calendar" Content="Saved...">
        <ToastPosition X="Right"></ToastPosition>
    </SfToast>
@code{
public async Task save(){
.....
        await ToastObj.Show();
....
}
}
Regards,
 Peter

3 Replies 1 reply marked as answer

IS Indrajith Srinivasan Syncfusion Team June 3, 2020 01:30 PM UTC

Hi Nemeth,

Greetings from Syncfusion support,

We have validated your reported query and able to reproduce the reported issue from our end. We will further validate on the reported issue and update you with more details in two business days by 5th June 2020.

Regards,
Indrajith


IS Indrajith Srinivasan Syncfusion Team June 5, 2020 02:13 PM UTC

Hi Nemeth,  
  
Greetings from Syncfusion support, 
  
We have validated your reported query and have considered “Script error occurs when opening the SfToast” as a bug from our end and logged the report for the same and the fix will be included with our patch release on the second week of June 2020. 
 
You can now track the current status of the report, review the proposed resolution timeline, and contact us for any further inquiries through this link: https://www.syncfusion.com/feedback/15003/
 
  
Regards,  
Indrajith 



IS Indrajith Srinivasan Syncfusion Team June 10, 2020 02:22 PM UTC

Hi Nemeth,

Thanks for your patience,

We have resolved the issue “Script error occurs when opening the SfToast” and the fix is available with the Nuget package version 18.1.56.
 
 
Can you please upgrade your package to this version to resolve the issue from your end? 
Regards, 
Indrajith 


Marked as answer
Loader.
Up arrow icon