mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2025-12-09 17:23:04 +03:00
Unable to download attachment after uploading via mobile client (Android/iOS) #1084
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Tieneks on GitHub.
Subject of the issue
Unable to download attachment after uploading via Android app. Downloading after uploading via web vault causes no issues.
Deployment environment
v1.25.1
Install method:
Docker image on Synology NAS
Clients used:
Web vault, Android app
Reverse proxy and version:
MySQL/MariaDB or PostgreSQL version:
SQLite
Other relevant details:
Steps to reproduce
Popup shows correct name and size of attachment.
The attached file does show up on the server in data/attachments/[FOLDER] with an expected size.
Expected behaviour
Uploading an attachment via the Android app should allow you to download the attachment later from any client.
Actual behaviour
The attachment is "gone" after uploading it via the Android app, cannot be downloaded and can only be removed.
Troubleshooting data
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden:
@tmeckel commented on GitHub:
I'm not sure if this is related, but when I try to upload an attachment via the WebVault the following pop-up is shown:
@tmeckel commented on GitHub:
@Tieneks Okay, so unrelated 👍🏼
@Tieneks commented on GitHub:
I do not get this error when uploading via the web vault.
@BlackDex commented on GitHub:
@Tieneks well, i have it patched, but not fixed.
With the latest version you will not be able to upload files via the mobile clients anymore.
That at least solves the issue of broken files, while a successful upload was reported.
We are looking into a better way to actually fix this.
@BlackDex commented on GitHub:
@Tieneks Hmm that is strange.
There seems to be something wrong with either the data transfered or stored.
Not sure yet what/how/why
@BlackDex commented on GitHub:
@hendrik1120 works fine for me. I suggest to check the reverse proxy settings and logs.
Also try to use the developer mode to debug the extension.
@Tieneks commented on GitHub:
I tested it and am getting an error message, as expected. Now at least the file won't "disappear".
It's not possible to upload a file as an attachment or Send from the Android app. When I upload a file via the web interface, I am able to download the file via the Android app. Again, as expected.
tl;dr:
Patch works as expected.
@hendrik1120 commented on GitHub:
It also happens with the chrome extension and even files saved months before are getting downloaded as 8 byte files.
This is gamebreaking. How are people supposed to get their security certs?
Edit: Same with the safari extension