Joplin 2.12.10 download the new version for android

Or we compress the app and release a would you mind doing some tests to see what would work? Or if you have other suggestions let me know.

dmg)? But we need to check that the old code will not pick that version. The problem is to know how long we should wait? Maybe 3 months? But from experience some users update 6 months or even a year or two later, and then they'll still end up with a broken app.Īs an alternative, I'm thinking we could release the ARM64 with a different extension.

At this point, we can start releasing the ARM64 version again. dmg properly) and wait x months to make sure everybody has the latest version.

I've been thinking about it, and the obvious solution would be to release the next 2.12 (which can update the. And if the user doesn't have an Apple M1 the app no longer starts at all. dmg, possibly a random one (probably depends in which order GitHub returns the releases), and it means they may download the ARM64 version. Then when old apps (pre-2.12) try to update, then pick one of the. To give a full picture, the problem is that when the ARM64 version is built, it adds a.

Joplin 2.12.10 download the new version for android