Operating system
macOS
Joplin version
3.4.12
Desktop version info
Can't open joplin app at the moment
What issue do you have?
I use Joplin app on mac OS along with joplin-cli. Recently I started getting this error and Joplin app doesn't open for me anymore
Unknown profile version. Most likely this is an old version of Joplin, while the profile was created by a newer version. Please upgrade Joplin at https://joplinapp.org and try again.
Joplin version: 3.4.12
Profile version: 49
Expected version: 48
I am not sure if joplin-cli has upgraded the profile which is causing this issue.
This is the version of joplin-cli version stable 3.5.1 that I am using. joplin-cli is reading the profile fine for operations like export
It does look like one Joplin client has upgraded Joplin's internal profile (database) version to 49. The error is telling you that Joplin v3.4.12 can only read profile versions up to and including 48. You will need to install one of the pre-release versions that use the updated profile, most likely v3.5.9 as it is the latest. See below.
| Joplin |
Internal
Profile |
Release Type |
Release Date |
Notes |
| 3.5.9 |
49 |
Pre |
2025-11-30 |
|
| 3.5.7 |
49 |
Pre |
2025-11-22 |
|
| 3.5.6 |
49 |
Pre |
2025-10-29 |
|
| 3.5.5 |
49 |
Pre |
2025-10-18 |
INTERNAL PROFILE CHANGE |
| 3.5.4 |
48 |
Pre |
2025-10-10 |
|
| 3.4.12 |
48 |
Full |
2025-09-09 |
|
| 3.4.11 |
48 |
Full |
2025-09-09 |
|
| 3.4.10 |
48 |
Full |
2025-09-01 |
|
For your information, this page shows that the next full release of Joplin is due very soon in the first week of the New Year.
Thank you so much for the information that I was looking for. Is this information about internal profile change publicly available?
I don't think that it is. Internal profile version changes don't appear to be mentioned in the changelogs either.
That is why I have been checking pre-releases and noting it down myself when the internal profile changes. That way it is easier for me to help when someone gets stuck due to this as I can easily tell them how far back they can go before the only option is to delete everything and re-download from the server.
From what I have seen internal profile changes are not that common any more and only occur with pre-releases, normally as a part of a version update. So whilst this is not an unknown problem it normally only affects those who try out a pre-release version using their "live" data and for some reason want to revert.
Gotcha. Thank you for all the information. I normally normally only update to stable versions but it seems joplin-cli via brew doesn’t follow it. I am going to pin my joplin-cli version in brew to make sure this doesn’t happen again.
Thanks once again