Profile version mismatch when attempting to run `joplin --env dev`

Support
1

Operating system

Windows

Joplin version

3.6.14

Desktop version info

Joplin 3.6.14 (prod, win32)

Device: win32, 12th Gen Intel(R) Core(TM) i9-12900K
Client ID: 4fbbe25ec49c4e17a68389b04e907df3
Sync Version: 3
Profile Version: 49
Keychain Supported: Yes
Alternative instance ID: -
Sync target: OneDrive
Editor: Rich Text

Revision: 7e2765a

Backup: 1.5.1
Extra Markdown editor settings: 1.11.0
Freehand Drawing: 4.3.0
joplin-excalidraw-v2: 2.0.0
Lootboxes: 1.0.0
Repeating To-Dos: 1.0.8
Rich Tables: 1.6.4

What issue do you have?

I am trying to work on a plugin and run a separate instance of joplin with the --env dev command. I get an error saying the profile version is expected to be 50. The full dialog is in the screenshots.

Looking at this post Unknown profile version led me to try enabling and fetching pre-release versions, but there weren't any.

My current workaround is just adding the plugin path to my actual instance of joplin and testing there, but I was wondering if anyone knows of a proper way to address this issue. Thanks!

Screenshots

Screenshot 2026-06-11 221513.png
Screenshot 2026-06-11 221513.png560×582 11.3 KB

2

Did you build the app yourself? Because profile version 50 hasn't been released yet, and was only merged yesterday. So if you built it before, you need to run that version

3

if you don't need the existing data in the dev profile you could also just delete or rename the dev profile folder (joplindev-desktop) so it gets created new on launch

4

Thank you! This worked

5

I built the plugin template with yo joplin (but i don't think this affects the profile version)

I ran yarn install and yarn start in a separate joplin repo earlier in the day. I am unsure if this would affect the expected profile version. Re-installing the latest joplin version from the website .exe file resulted in the same error behavior in the screenshot.

6

I ran yarn install and yarn start in a separate joplin repo earlier in the day

yeah that explains it, when you run joplin with yarn start it uses the dev profile by default

so your dev profile was either created with (or updated to) version 50 by running the latest joplin code from github with yarn start, so when you then tried to run joplin v3.6 with the same dev profile it resulted in an error due to the profile version being newer than the one used by 3.6