SyncFusion.Blazor.FileManager -> NullReferenceException

We previously had a working FileManager. When we upgraded to 18.4 (replace Syncfusion.Blazor 19 with individual nugets) and made the changes regarding documentation SfFileManager<TValue> after that we started receiving this error:

System.NullReferenceException: Object reference not set to an instance of an object.
   at Syncfusion.Blazor.FileManager.SfFileManager`1.<>c__DisplayClass608_0.<BuildRenderTree>b__21(RenderTreeBuilder __builder5)
   at Microsoft.AspNetCore.Components.CascadingValue`1.Render(RenderTreeBuilder builder)
   at Microsoft.AspNetCore.Components.Rendering.ComponentState.RenderIntoBatch(RenderBatchBuilder batchBuilder, RenderFragment renderFragment)
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.RenderInExistingBatch(RenderQueueEntry renderQueueEntry)
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.ProcessRenderQueue()

We are able to reproduce in a separate vs project in attachement.

Best Regards.

Attachment: TestFileManager_6ee16496.zip

7 Replies 1 reply marked as answer

SP Sowmiya Padmanaban Syncfusion Team December 23, 2020 11:53 AM UTC

Hi Michaël Collard,  
 
Sorry for the inconvenience. 
 
We are able to replicate the issue. We have consider this as a bug from FileManager component your reported problem with FileManager component. We will include the fix for this bug in our next patch release which is expected to rolled out by the end of December 2020.  
  
You can track the status of this issue fix through the following feedback portal link.  
 
 
We appreciate your patience. 
 
Regards,  
Sowmiya.P 



SP Sowmiya Padmanaban Syncfusion Team December 30, 2020 11:23 AM UTC

Hi Michaël Collard,   
 
Thanks for your patience. 
 
We are glad to announce that our patch release (V18.4.32) is rolled out successfully. In this release, we have included fix  for Null reference exception occurs while setting ajax settings values as null”. To access this fix, we suggest you to update the package to the latest version (V18.4.32). 
 
Please, refer the below sample link. 
 
 
Please get in touch with us if you would require any further assistance. 
 
Regards, 
Sowmiya.P 



MC Michaël Collard January 14, 2021 02:51 PM UTC

Hi,
Best wishes for this new year.
I'm sorry for the long waiting time response.

Unfortunately FileManager doesn't works with these nuggets packages 18.4.030 || 31 || 32 || 33 || 34 :'(
We are able to reproduce in a separate vs solution.
Last time i forgot to wrote that we use FileManager with a s3Provider.

We need to have something usefull cause we'll deploy in a few time app in production.
In vs solution in attachment you'll find in root folder s3FileProvider && s3Controller desactivated classes, that we previously used with success.

If you see something goes wrong, please let us know.

Thank'in advance.

Best Regards.


Attachment: TestFileManager2061405981_e674406c.zip


SP Sowmiya Padmanaban Syncfusion Team January 15, 2021 10:30 AM UTC

Hi Michaël Collard,  
 
Sorry for the inconvenience. 
 
We have facing some issue in integration of Amazon S3 Bucket with FileManager component. We have already fixed the issue and the fix is in testing phase. We will include the fix for this issue in upcoming patch release which is expected to be released at the mid of next week January 2021. 
 
You can track the status of your reported problem through the below portal link, 
 
 
We appreciate your patience. 
 
Regards,  
Sowmiya.P 



SP Sowmiya Padmanaban Syncfusion Team January 20, 2021 10:29 AM UTC

Hi Michaël Collard, 
 
We are glad to announce that our patch release (V18.4.35) is rolled out successfully. In this release, we have included fix for “AmazonS3 Bucket in FileManager component”. To access this feature, we suggest you to update the package to the latest version (V18.4.35). 
 
Please, refer to the below GitHub link for updated Amazon service. 
 
 
Please, refer to the sample link below. 
 
 
Note: You need to replace the amazon credentials in controller method. 
 
this.operation.RegisterAmazonS3("<---bucketName--->", "<---awsAccessKeyId--->", "<---awsSecretAccessKey--->", "<---region--->"); 
 
We thank you for your support and appreciate your patience in waiting for this release. Please get in touch with us if you would require any further assistance. 
 
Regards,  
Sowmiya.P  


Marked as answer

MC Michaël Collard January 26, 2021 07:30 AM UTC

Nice, it works great right now , thanks a lot :-)


KR Keerthana Rajendran Syncfusion Team January 27, 2021 07:53 AM UTC

Hi Michaël Collard,  
 
Most Welcome. We are glad to hear that the issue has been resolved in your end. Please get back to us if you need further assistance. We will be happy to assist you. 
 
Regards, 
Keerthana.  


Loader.
Up arrow icon