bitwarden / bitwarden/server

import of bitwarden json export failed with "An error has occurred." when using sqlite

Open
#7,955 8 comments 1 reaction 0 assignees View on GitHub
bug bw-lite-deploy
Dominant language
C#
Stars
20.1k
Forks
1.8k
Avg merge
4d 8h
Merged PRs (30d)
75

Description

### Steps To Reproduce

- fresh deploy of latest bitwarden lite with sqlite as db engine
- create account
- start import of a bitwarden json export

### Expected Result

- import succeeds

### Actual Result

- import failed with a popup "An error has occured."

### Screenshots or Videos

_No response_

### Additional Context

import with the same setup but with mariadb as db engine finished successfully

### Githash Version

{"version":"2026.4.1","gitHash":"3371bb61","server":null,"environment":{"cloudRegion":null,"vault":"https://bitwarden.crack-n-hack.org","api":"https://bitwarden.crack-n-hack.org/api","identity":"https://bitwarden.crack-n-hack.org/identity","notifications":"https://bitwarden.crack-n-hack.org/notifications","sso":"https://bitwarden.crack-n-hack.org/sso"},"featureStates":{},"push":{"pushTechnology":0,"vapidPublicKey":null},"communication":null,"settings":{"disableUserRegistration":false},"object":"config"}

### Environment Details

- Arch Linux
- Docker
- VM Intel 2 cores

### Database Image

_No response_

### Issue Tracking Info

- [ ] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

Contributor guide

Open the contributing guide

Research direction

No file, test, or entry point is named in the issue. Reproduce the Bitwarden JSON import with a fresh SQLite deployment, inspect the server logs for the popup's underlying error, and compare the result with MariaDB; done means the import completes successfully on SQLite.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, docker, sqlite
Domain
backend, database
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.