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
When Downloading files from proton drive, I get the following error message. I do not get asked, where this file shall be stored, and I do not see the file stored anywhere in my filesystems.
Unhandled Promise Rejection
Error: Failed to resolve file system resource directory from the "webclient://mail.proton.me/sw/2" request
at resolveFileSystemResourceLocation (/opt/ElectronMail/resources/app.asar/app/electron-main/index.cjs:75939:57)
at AsyncFunction. (/opt/ElectronMail/resources/app.asar/app/electron-main/index.cjs:75973:42)
Please advice
Kind regards
Daniel
The text was updated successfully, but these errors were encountered:
Downloading worked fine at my side on 21MB mp3 file. It might be size-dependent, but I didn't test a larger file yet. The ServiceWorker involving (webclient://mail.proton.me/sw/2 part from your log) might be depending on the downloaded file size (a possible reason why the error didn't occur on my test 21MB file size case), so some debugging and proton's code reviewing will be needed.
Thank you. You are right. A single 5MB file worked fine. I just wanted to copy down everything from Proton Drive to my new linux laptop, multiple recursive directories downloaded as a zip file of around 20-50GB sizes.
When Downloading files from proton drive, I get the following error message. I do not get asked, where this file shall be stored, and I do not see the file stored anywhere in my filesystems.
Unhandled Promise Rejection
Error: Failed to resolve file system resource directory from the "webclient://mail.proton.me/sw/2" request
at resolveFileSystemResourceLocation (/opt/ElectronMail/resources/app.asar/app/electron-main/index.cjs:75939:57)
at AsyncFunction. (/opt/ElectronMail/resources/app.asar/app/electron-main/index.cjs:75973:42)
Please advice
Kind regards
Daniel
The text was updated successfully, but these errors were encountered: