An error occurs when selecting a folder while importing messages or entities

[v-xianya]

Storage Explorer Version

1.41.0

Regression From

Not a regression

Architecture

x64

Storage Explorer Build Number

20260119.4

Platform

Linux (tar.gz)

OS Version

Linux Ubuntu 22.04

Bug Description

When importing messages into a queue / Importing entities into a table in Storage Explorer, selecting a folder instead of a file causes the operation to fail with an unclear error. After clicking Import and choosing a directory (for example, ~/Downloads), Storage Explorer displays the error:

Unable to parse import file '/home/.../Downloads'. Details: EISDIR: illegal operation on a directory, read.

This issue doesn't reproduce for snap installed storage explorer.

Resource Types

Queues, Tables

Authentication Method

None

Connection Type

Sign in (subscription)

Steps to Reproduce

1. Download the Storage Explorer .tar package and extract it.
2. Navigate to the extracted folder and launch Storage Explorer.
3. Expand a storage account -> Queues.
4. Select a queue and click -> Import.
5. Select one Folder (.e.g., Downloads) -> Click Select.
6. Check the result.

Actual Experience

Storage Explorer allows selecting a folder and then fails with the error:

Expected Experience

Storage Explorer should prevent selecting a folder for import or display a clear validation message indicating that only files are supported.

Additional Context

Here is the gif:

[craxal]

@v-xianya It's clear that the item selected is a directory, not a file, so the error is expected. We can probably harden that by making sure folders are not selectable.

The snap should not be accepting folders. What happens when you select the folder and close the dialog in the snap? Does it show the path to the folder in the import file field?

[v-xianya]

@craxal Here is the behaviors in snap:

[craxal]

We are already using the correct openFile option, so looks like this is an issue with Electron or Linux. Considering this isn't blocking anything (the dialog doesn't try to import anything), I don't think this is a serious issue.