FileManager error since version 29.x

Hi everybody,

  I am using Filemanager to load a md file into RTE. This was working fine in version 28.x. After changing to 29.x, 

I get the following error:

at Syncfusion.Blazor.FileManager.Internal.FileManagerGridView`1.OnUnSelection(RowDeselectEventArgs`1 args)

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

   at Syncfusion.Blazor.Grids.Internal.Selection`1.ClearRowSelection(Row`1 except, MouseAndKeyArgs evt)

   at Syncfusion.Blazor.Grids.Internal.Selection`1.SelectRows(Object rowIndexes)

   at Syncfusion.Blazor.Grids.SfGrid`1.SelectRowsAsync(Int32[] rowIndexes)

   at Syncfusion.Blazor.FileManager.Internal.FileManagerGridView`1.SelectRowsAsync(String[] selectedItems)

   at Syncfusion.Blazor.FileManager.Internal.FileManagerGridView`1.UpdateSelection()

   at Syncfusion.Blazor.FileManager.Internal.FileManagerGridView`1.OnAfterRenderAsync(Boolean firstRender)

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

   at Microsoft.AspNetCore.Components.WebView.IpcSender.<>c__DisplayClass12_0.<NotifyUnhandledException>b__1()

   at Microsoft.AspNetCore.Components.WebView.WindowsForms.WindowsFormsDispatcher.InvokeAsync(Action workItem)

   at Microsoft.AspNetCore.Components.WebView.WindowsForms.WindowsFormsDispatcher.<>c.<.cctor>b__8_0(Exception exception)

   at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)

   at System.Reflection.MethodBaseInvoker.InvokeDirectByRefWithFewArgs(Object obj, Span`1 copyOfArgs, BindingFlags invokeAttr)

This happens in BlazorWebView and in a Blazor Server App.

Did I miss any breaking changes or do I have to update FileManagerService.cs or is it just a bug ?

   regards

       Uwe



5 Replies

LD LeoLavanya Dhanaraj Syncfusion Team April 14, 2025 10:13 AM UTC

Hi Uwe,


Greetings from Syncfusion support.


We have prepared and attempted to replicate the mentioned error in the Blazor FileManager sample using a physical file provider. We suspect that issue pertains to the selection feature in the details view of the FileManager.


We tried to replicate the issue using the specified version (28.x.x) as well as the latest version (29.x.x) across different browsers (Chrome, Edge, and Firefox) and various selection scenarios, such as using checkboxes, keyboard input, direct selection/deselection of items, and selection after performing actions like renaming, uploading, and creating new folders. However, we were unable to replicate the issue, both with the hosted URL and by connecting with individual providers.


For your reference, we have included video footage along with the tested sample.


Sample: Attached as a zip file.


Provider : https://github.com/SyncfusionExamples/ej2-aspcore-file-provider


Also, we suspect that the problem may be related to either the browser cache or the NuGet cache, especially after updating to a newer version. To help resolve the issue, we recommend removing the bin and obj folders from your project and then rebuilding and clearing your browser cache.


We have attached a blog post that provides step-by-step instructions for clearing the cache to assist you in this process.


To clear the NuGet cache - https://support.syncfusion.com/kb/article/6265/how-to-clear-nuget-cache?isInternalRefresh=False 


To clear the browser cache - https://support.google.com/accounts/answer/32050?hl=en&co=GENIE.Platform%3DDesktop 


Please check this on your end and if the issue persists, kindly replicate it in the provided sample or share a sample where the issue can be reproduced(if possible, provide a replication step as a video footage). This will help us investigate further and provide you with a prompt resolution. We look forward to your response with the requested details.


Regards,

Leo Lavanya Dhanaraj


Attachment: FileManager_29.x.x_49f27d84.zip


UH Uwe Hein replied to LeoLavanya Dhanaraj April 14, 2025 11:55 AM UTC

Hi Leo,

  I attach a sample based on the ones you provided. Here the FileManager Dialog opens OK when clicking on the left most button of the toolbar when using version 28.2.12 whereas the dialog freezes using version 29.1.36. You can easily change versions in the csproj file for testing.  In version 29x no error msg is shown anywhere.

This is not quite the same behaviour I mentioned in my first post, but it might be related to this.

   regards

      Uwe


Attachment: RTE_Filemanager_Flat_631da824.zip



UH Uwe Hein April 24, 2025 08:30 AM UTC

Hi Leo,


  could you run my sample in 29.x without problems ?


      Regards

         Uwe

         



PM Prasanth Madhaiyan Syncfusion Team April 28, 2025 12:21 PM UTC

Hi Uwe Hein,

Upon further validation, we were able to replicate the reported issue where the Blazor Dialog popup opens with a delay when rendering the FileManager component. We have already considered this as a bug, and the fix will be included in the weekly patch release scheduled for April 29, 2025.

You can track the status of the fix through the following link.


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.

Regards,

Prasanth Madhaiyan.



LD LeoLavanya Dhanaraj Syncfusion Team April 30, 2025 02:11 PM UTC

Hi Uwe Hein,


We are glad to announce that our patch release (V29.1.40) has been rolled out successfully.  The issue where “Facing an issue where the BeforeImageLoad event is being triggered continuously in the Blazor FileManager” has been resolved in this release.


To access this fix, we suggest you update the package to 29.1.40 and we include the sample in the latest version for your reference.


Sample : Attached as a zip file.


Feedback : https://www.syncfusion.com/feedback/67117/facing-an-issue-where-the-beforeimageload-event-is-being-triggered-continuously-in


Release noteshttps://blazor.syncfusion.com/documentation/release-notes/29.1.40?type=all#file-manager


Root cause : The reported issue occurs due to using the CopyToAsync method from the System.IO library to copy stream data.
Since the underlying stream does not support true asynchronous operations properly, the method does not return any data and the code following CopyToAsync is not executed. As a result, the event continues to trigger repeatedly without throwing any exceptions.


Regards,

Leo Lavanya Dhanaraj


Attachment: RTE_Filemanager_Flat_41517222.zip

Loader.
Up arrow icon