You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Snap instances doesn't support multi-select in upload dialog #5780
Storage Explorer Version: 1.25.0-dev Build Number: 20220525.1 Branch: main Platform/OS: Linux Ubuntu 20.04 Architecture: ia32 How Found: From running test cases Regression From: Previous release (1.23.1)
Steps to Reproduce
Expand one storage account -> Blob Containers.
Create a blob container -> Click 'Upload -> Upload Files'.
Click 'No files selected' box -> Select two files.
Click 'Open- > Upload' -> Check whether succeeds to upload two files.
Expected Experience
Succeed to upload two files.
Actual Experience
Fail to upload two files, only one file displays in the explorer.
Additional Context
This issue also reproduces for file shares.
This issue doesn't reproduce on Storage Explorer which is installed by tar.gz.
changed the title [-]Fail to upload more than one file at the same time on Storage Explorer which is installed by snap[/-][+]Snap instances doesn't support multi-select in upload dialog[/+]on May 26, 2022
People on more recent versions of the library won't have this issue. Since the team is backporting the fix, we are going to make this a known issue without making any code change for now.
Activity
MRayermannMSFT commentedon May 25, 2022
v-kellyluo does this repro with 1.24.0 or 1.24.1?
v-kellyluo commentedon May 26, 2022
Matthew Rayermann (@MRayermannMSFT) Yes, this issue reproduces with 1.24.1😢.
[-]Fail to upload more than one file at the same time on Storage Explorer which is installed by snap[/-][+]Snap instances doesn't support multi-select in upload dialog[/+]JasonYeMSFT commentedon May 26, 2022
This is due to an external bug in a library snap uses. https://forum.snapcraft.io/t/wrong-file-path-of-opened-files-in-snap-apps/22982
People on more recent versions of the library won't have this issue. Since the team is backporting the fix, we are going to make this a known issue without making any code change for now.