When Notifacations has updated to latest version.
Hi Robert ,
We have considered the reported issue "Error Message: System.ArgumentException in Blazor Web Assembly Application" as a bug from our end, and the fix for the issue will be included in our upcoming patch release, which is expected to roll out at the end of April.
Now you can track the status of the reported issue through the feedback below,
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.”
I get the same error in the latest version.
As per the last update, the fix will be included for "Error Message: System.ArgumentException in Blazor Web Assembly Application" in our upcoming patch release, which is expected to roll out at the end of April. Please be patience until then.
We would like to inform you that our 2023 Volume 1 SP Release has been scheduled for the first week of May 2023. Therefore, we will not have a weekly patch release this week (April 26, 2023). We will include a fix for the issue "Error Message: System.ArgumentException in Blazor Web Assembly Application" in our upcoming Volume 1 SP release.
I'm also getting this for Blazor Server.
Yes. This issue also occurs on the Blazor server application. As per our last update, we will include a fix for the issue "while rendering the Toast component, a console error occurred" in our upcoming Volume 1 SP release. Please have patience until then.
Hi, I am also getting this error in WASM. Is there a work around? I can't upgrade without this.
Yesterday I updated to the new release of syncfusion blazor and I am still getting this error. Was It addressed and something else is happening or is it still being worked on? A progress update would be great as my understanding is that the service pack mentioned above was released and I am not sure if the problem still exists or I have something else causing a similar message.
After reviewing the information you provided, we suspect that the issue may be related to the cache not being cleared. To resolve this, we recommend that you try using the CDN link provided below.
Using this link can help resolve the issue. If you continue to face the issue even after using the CDN link, please let us know, and we will be happy to assist you further.