Same issue here. "have you downloaded from F-droid?" feels like shifting the blame as this never happened before. Maybe have both versions at the same level like they were always up to now.
Thanks! I don't change anything on my devices. I have all stable app in my Android and my linux.
Works for me (Debian 13) updating to pre-release with wget -O - ``https://raw.githubusercontent.com/laurent22/joplin/dev/Joplin_install_and_update.sh`` | bash -s -- --prerelease
I don't think Joplin controls the version that's available on f-droid, its a community maintained package
F-Droid always used pre-releases (i.e. there was no distinction between stable releases and pre-releases there), it's just that the sync target happened to still be compatible with the stable versions, so they both worked together with no issues.
They have now fixed it and pull the stable releases
That's not exactly true. I remember that the same happened six years ago when a pre-release that upgraded the sync version was put out on F-Droid causing those affected to have to update all their clients to a compatible version.
Maybe use pre-release tags like "-alpha", "-beta", "-rc" ?
Hello,
I think also for me the fdroid app caused the problem. I synchronise via the filesystem (and that synchronises via syncthing) to Windows and Linux desktops.
When I now change my release channel to pre-release I am worried that I can never get back to the normal stable channel. I am not particularly keen in using a beta or even alpha version with my notes.
How would I handle the situation in September when the stable 3.7x is released? Would I run into issues because at that point the pre-release version will be even further ahead than 3.7?
Many thanks for your advice 
This worked perfect for me!!
Joplin on linux mint and the f-droid version on my e/os smartphone.
Thank you!
As long as you switch back to the stable channel after then you should be fine even if you go beyond 3.7.x in a pre-release.
If I recall, it was due to a schema change on the sync data. So as long as the next pre-release doesn't immediately have a schema change then you should be fine switching to a stable release in general.
I am not a dev but from what I have seen and experienced Joplin pre-releases are more a "Release Candidate" than a traditional alpha or beta testing version.
No
Just ensure that the "get pre-releases" box in the settings is unchecked...
... and you will resume only being notified about those versions Joplin publishes as the latest (or "full") release.
Hello,
I work on Pop!_OS 24.04 LTS and I have followed the advice about the prerelease that was given on this Forum, i‧d. the command "wget -O - https://raw.githubusercontent.com/laurent22/joplin/dev/Joplin_install_and_update.sh | bash -s -- --prerelease"
Then, the terminal answered "installed" and "updated". So, I presume it's done but I just can't open it and I don't even know where he is. Should I first uninstall the flathub version ?
Thank you for your attention ?
I am not familiar with Pop!_OS but some distros may need the user to log out and back in again before the icon appears and the app can be searched for.
On Linux the install script downloads the AppImage to ~/.joplin/.
Hello. I am in a similar situation here. I have a series of devices that sync together : 2 Android mobile phones, 4 Linux PC and 1 Windows PC that uses the web app as I don't have administrator rights for that one. The sync server is Dropbox.
One of the devices (Android) got updated to 3.7 through F-Droid and now all the other ones won't sync (save for the web app).
It seems easier to me to export the data, downgrade the Android device back to 3.6.2, reimport the data and resync the data with the server.
But that still won't sync because somehow, on the Dropbox server, it is written that it should be version 3.7 or higher.
What should I do with the server to make it work ?
Just wipe out the whole /Apps/Joplin folder on the Dropbox server ?
Here's how I solved a similar situation:
Hello Muzak. Thanks for the reply.
Actually, in the meantime, I have solved the issue the following way :
- I have exported my Joplin notes as a .jex file. If you are in doubt if all of the version of your notes are the same on all devices, I suggest export them from each device as .jex files, but also as markdown files and use text files comparison software.
- On the device with Joplin 3.7 (an Android), I have uninstalled Joplin and reinstalled the version 3.6, and then I have imported the .jex file.
- On my Dropbox account, I have changed the name of the Apps/Joplin folder to Apps/Joplin.BAK.(current date).
- I have set up again the sync for the device with the reinstalled Jopin. It creates a new Apps/Joplin folder in Dropbox. Wait for the sync to complete.
- Now re-sync each one of the other devices, one device at a time make sure the others won't sync at the same time).
You may need to re-enable sync with your Dropbox account.
Also, on the syncing device, it created duplicates of every root notebook. So I advice that you temporarily rename your root notebooks by adding a suffix. Delete the duplicates.
I also advise to do a back-up of the Apps/Joplin folder after each time you have synced a different device.