"A task was canceled" exception

[TravisNorwood]

We are frequently getting errors like this recorded in our error logs. These errors are not showing up consistently that we can tell. Lots of instances of using BlazoredModal don't get this error.

Exception:A task was canceled.
Stack Trace:   at Microsoft.JSInterop.JSRuntime.InvokeAsync[TValue](Int64 targetInstanceId, String identifier, Object[] args)
   at Microsoft.JSInterop.JSRuntimeExtensions.InvokeVoidAsync(IJSRuntime jsRuntime, String identifier, Object[] args)
   at Blazored.Modal.BlazoredModal.Update(ModalReference modalReference)
   at Microsoft.AspNetCore.Components.Rendering.RendererSynchronizationContext.ExecuteSynchronously(TaskCompletionSource`1 completion, SendOrPostCallback d, Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
   at Microsoft.AspNetCore.Components.Rendering.RendererSynchronizationContext.ExecuteBackground(WorkItem item)

[larsk2009]

Hmmm, update does call BlazoredModal.activateScrollLock through JS interop, so that is probably the task that gets cancelled. When you see this, do you get any errors in the browser console? You might have to run in debug mode for that. I would suspect that the JS is somehow failing and that get the task cancelled? Other option is something where the modal gets destroyed or something and that gets the task cancelled.

I can't recall anyone reporting this issue before, so if you could provide some more information or a way to reproducing this that would be great!

[TravisNorwood]

Unfortunately we can't replicate the error. It just shows up on the logs on production sites. We've spent a while trying to replicate to no avail. From: Lars Koopmans ***@***.***> Sent: Thursday, February 3, 2022 11:59 To: Blazored/Modal ***@***.***> Cc: Travis Norwood ***@***.***>; Author ***@***.***> Subject: Re: [Blazored/Modal] "A task was canceled" exception (Discussion #384) Caution: This email originated from outside of the organization! Do not click links or open attachments unless you recognize the sender and email address and know the content is safe. .

…

________________________________ Hmmm, update does call BlazoredModal.activateScrollLock through JS interop, so that is probably the task that gets cancelled. When you see this, do you get any errors in the browser console? You might have to run in debug mode for that. I would suspect that the JS is somehow failing and that get the task cancelled? Other option is something where the modal gets destroyed or something and that gets the task cancelled. I can't recall anyone reporting this issue before, so if you could provide some more information or a way to reproducing this that would be great! — Reply to this email directly, view it on GitHub<#384 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AITIVFY5GDZ6PNA5C7QL2C3UZK647ANCNFSM5NPTFEYA>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[larsk2009]

Hmmm, that makes it difficult. I think it would be best if you create an issue instead of a question here, than we can track it there and if other people have the same issue we can collect all the info there.