Vault export - Where did it go?

Hi,

Just ran a vault export from Vivaldi using the browser extension. I was not prompted for a filename. The export appeared to proceed but I have no idea where the file is. Does not appear to be in downloads, and nothing obvious is under my Windows user folder.

Open C:\ in file explorer, then search for one of these:

datemodified:today

or

bitwarden*export

@wobbly_bob Can confirm that it seems to be a bug on Vivaldi. I just tried it with Brave, and there I was asked where to save the file.

PS: I reported it as a bug on GitHub. - For now, I would advise to export via another browser extension (e.g. I just tested it successfully on Brave) or directly via the web vault.

No files named similarly anywhere on C:.

Thanks, will do. Would you mind providing a link to the github bug report?

→ You can add your info, if you want to!

In that case, it seems that there was no actual export, so nothing to worry about from a “data exposure” perspective. My money is on the bug that @Nail1684 mentioned.

You do still need to worry about “data loss”. For that, I would create an export using one of the desktop app, the web vault or the extension in a more main-stream browser.

Thanks @Nail1684, appreciate you raising the bug.

1 Like

A little bit late, but a short update to that. My issue was closed as a “duplicate” - seems to be that there is a long-standing issue with Vivaldi regarding some operations of the extension.

Workaround: pop out the extension window on Vivaldi, when you want to make an export (and probably also for working with “attachments”).

Here the relevant explanatory comment to my GitHub issue: Export fails on Vivaldi · Issue #12945 · bitwarden/clients · GitHub (including links to the older relevant issues)

PS: As this seems to remain a bug for the time being (as I understand it, it depends on Vivaldi itself resolving a “bug”) and as there is a workaround (to pop out the extension window), I will mark this post now as “solution” (again, for the time being)…

PPS: Thanks @grb for adding the active GitHub issue “for future reference”! To have everything under the “solution”, here also the link…:

For future reference, here is the active GitHub Issue:

1 Like