1. Home
  2. Forum
  3. Blazor
  4. Unhandled exception on FileManager file download

Unhandled exception on FileManager file download

I'm working on a sample FileManager Blazor server-side project - and am getting an unhandled exception when downloading a file.  I'm getting the error both in the sample Blazor app as well as my own.  It appears it's coming from blazor.server.js and is a recent bug introduced by MS that they are in the process of fixing.  Just wanted to confirm/verify that there's nothing I'm overlooking.


The files are actually downloading fine, but you have to reload the Blazor app after every download to refresh the UI - it simply vanishes.


5 Replies 1 reply marked as answer
SP Sowmiya Padmanaban Syncfusion Team October 1, 2020 12:35 PM UTC

Hi Mark Peterson, 
 
Greetings from Syncfusion support. 
 
We have checked your reported issue with FileManager component. But, we were unable to reproduce it. Folders are downloaded properly in FileManager component. 
 
Refer the attached video for downloading a folder. 
 
 
Refer the below sample link. 
 
 
1.     Could you please share us the more details regarding your reported issue. 
2.     Share the .NET SDK version used in your application. 
3.     Share the Syncfusion.Blazor NuGet version used in your application. 
4.     Which file provider service you have used for FileManager component? Refer the below link to know about the file provider services available in FileManager component. 
 
Please let us know, if you need any further assistance. 
 
Regards, 
Sowmiya.P 


LU Luca October 29, 2020 12:38 PM UTC

We're facing the same issue in our application. File downloads but an exception is thrown, and users have to reload the page. 
Syncfusion blazor package version is 18.3.0.42
.NET Core version is 3.1.403


Exception is:
Error: Circuit has been shut down due to error.
e.log@blazor.server.js:19
C@blazor.server.js:8
(anonymous)@blazor.server.js:8
(anonymous)@blazor.server.js:1
e.invokeClientMethod@blazor.server.js:1
e.processIncomingData@blazor.server.js:1
connection.onreceive@blazor.server.js:1
i.onmessage@blazor.server.js:1


SP Sowmiya Padmanaban Syncfusion Team October 30, 2020 03:09 PM UTC

Hi Luca,  
 
We have checked your reported problem with FileManager component. But unfortunately, we were unable to replicate it from our end. 
 
Refer the below FileManager link. In this sample, we have using (18.3.42) Syncfusion.Blazor package. 
 
 
Download is working properly in the above sample. Could you please check the above sample. 
 
We are not facing any issue in our sample browser site too. 
 
 
If the issue still persist, share the below details. 
 
1.     Are you using client or server side application. 
2.     Which file provider service you have used for FileManager component? Refer the below link to know about the file provider services available in FileManager component.  
3.     If possible, replicate the issue in attached sample. 
 
Please let us know, if you need any further assistance. 
 
Regards,  
Sowmiya.P 


JL jose luis barajas June 25, 2021 02:12 AM UTC

Hi

I get this exception donwloading files with version 19.1.0.66 in blazor wasm project...

please help


Uncaught ReferenceError: Blazor is not defined

    at 2526:64

/authentication/logi…82115DC5E29C5F8B:64 Uncaught ReferenceError: Blazor is not defined

33blazor.webassembly.js:1 info: Microsoft.AspNetCore.Authorization.DefaultAuthorizationService[1]

      Authorization was successful.

blazor.webassembly.js:1 crit: Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100]

      Unhandled exception rendering component: Arg_NullReferenceException

System.NullReferenceException: Arg_NullReferenceException

   at Syncfusion.Blazor.FileManager.SfFileManager`1.<UpdateSelectedItems>d__580[[Syncfusion.Blazor.FileManager.FileManagerDirectoryContent, Syncfusion.Blazor.FileManager, Version=19.1.0.66, Culture=neutral, PublicKeyToken=null]].MoveNext()

   at Syncfusion.Blazor.FileManager.Internal.FileManagerContextMenu`1.<OpenContextMenu>d__67[[Syncfusion.Blazor.FileManager.FileManagerDirectoryContent, Syncfusion.Blazor.FileManager, Version=19.1.0.66, Culture=neutral, PublicKeyToken=null]].MoveNext()

   at Syncfusion.Blazor.FileManager.SfFileManager`1.<OpenContextMenu>d__593[[Syncfusion.Blazor.FileManager.FileManagerDirectoryContent, Syncfusion.Blazor.FileManager, Version=19.1.0.66, Culture=neutral, PublicKeyToken=null]].MoveNext()

   at Microsoft.AspNetCore.Components.ComponentBase.CallStateHasChangedOnAsyncCompletion(Task task)

   at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task taskToHandle)

d.printErr @ blazor.webassembly.js:1

2blazor.webassembly.js:1 info: Microsoft.AspNetCore.Authorization.DefaultAuthorizationService[1]

      Authorization was successful.

2blazor.webassembly.js:1 info: Microsoft.AspNetCore.Authorization.DefaultAuthorizationService[1]

      Authorization was successful.



SM Shalini Maragathavel Syncfusion Team June 25, 2021 12:10 PM UTC

Hi Jose, 

Good day to you. 
                                                                        
We have validated your reported problem, but unfortunately we were unable to reproduce it at our end as the download operation of File Manager component is working fine in the v19.0.1.66.  

We have attached our validated demo sample for your reference below. 


If your reported problem still persists, then please share us the following information. 

  • Let us know which file provider service that you are using with FileManager component in your application.

Check out the following link to know the available file provider services for FileManager component. 
 
  • If possible, replicate your reported problem above provided sample.
 
  • Share us video demo to reproduce your reported problem at our end.
 
This information would help us to find the exact cause of your reported problem and to provide you the prompt solution. 
Regards,  
Shalini M. 


Marked as answer
Loader.
Up arrow icon