ARM build for mac os M1 processor

[rafjaf]

Hello, apparently Joplin 2.6.10 for macos is only optimized for intel-based Mac. Yet buiding Electron apps compatible with ARM proessors seems possible, see https://www.electronjs.org/blog/apple-silicon. Is there any plan to implement this? Thank you in advance for considering this issue.

[sbkg0002]

Also wondering.

[Joey-0812]

Also wondering.

[ridicolos]

Would love to see a native m1 version as well.

[sbkg0002]

Is there a way I can help to fix this? I can update/create a Github workflow or something if needed.

[Shamp0o]

For reference: There's a discussion about building the app for arm64 on the forum, including some successful builds.

I'm happy to help with testing in order to get official arm64 builds for everyone.

[runchard]

I've done a PR with #5537 but failed to merge due to lack of tests.
And to be honest, I can't figure out what kind of platform dependent test is needed here.

[github-actions]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[rafjaf]

Hi, I still believe the issue to be relevant for the community, as show the discussions on the forum : https://discourse.joplinapp.org/t/running-joplin-on-apple-silicon/11455

[github-actions]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[sbkg0002]

Hi, I still believe the issue to be relevant for the community, as show the discussions on the forum : https://discourse.joplinapp.org/t/running-joplin-on-apple-silicon/11455

Same here. Looking for an alternative since this feels hopeless.

[Bringoff]

Here's what a long AOT-compilation looks like on my MBP with M1 Pro.

Screen.Recording.2022-05-22.at.13.01.04.mov

[github-actions]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[ajgraves]

Answering the bot; this issue is still relevant and outstanding. See https://discourse.joplinapp.org/t/running-joplin-on-apple-silicon/11455. Though it's definitely stagnated a bit.

[github-actions]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[ajgraves]

Answering the bot again; this issue is still relevant and outstanding. See https://discourse.joplinapp.org/t/running-joplin-on-apple-silicon/11455.

[github-actions]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[skymagician]

this issue is still relevant and outstanding.

[guiix-code]

Still relevant

[Nctllnty]

Still relevant

[laurent22]

Hi everyone, a new ARM64 release is available here: https://github.com/laurent22/joplin/releases/tag/v2.12.7

[rafjaf]

Thank you very much @laurent22 for the efforts put into solving this issue!

[lethargosapatheia]

In my case the sync is still not working. I get the same error as before, a difference that stands out now is that it does say "Completed":

Completed: 13/07/2023 17:51 (22s)

Which is misleading, because it doesn't actually synchronise anything.

This is the full error in the console (very similar if not identical to the previous ones):

Synchronizer: Error: GET info.json: No public access to this resource., No 'Authorization: Basic' header found. Either the client didn't send one, or the server is misconfigured, No 'Authorization: Bearer' header found. Either the client didn't send one, or the server is mis-configured, No 'Authorization: Basic' header found. Either the client didn't send one, or the server is misconfigured (Exception Sabre\DAV\Exception\NotAuthenticated) (401): <?xml version="1.0" encoding="utf-8"?>
<d:error xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns">
  <s:exception>Sabre\DAV\Exception\NotAuthenticated</s:exception>
  <s:message>No public access to this resource., No 'Authorization: Basic' header found. Either the client didn't send one, or the server is misconfigured, No 'Authorization: Bearer' header found. Either the client didn't send one, or the server is mis-configured, No 'Authorization: Basic' header found. Either the client didn't send one, or the server is misconfigured</s:message>
</d:error>

    at newError (/Applications/Joplin.app/Contents/Resources/app.asar/node_modules/@joplin/lib/WebDavApi.js:414:11)
    at WebDavApi.exec (/Applications/Joplin.app/Contents/Resources/app.asar/node_modules/@joplin/lib/WebDavApi.js:441:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async FileApiDriverWebDav.get (/Applications/Joplin.app/Contents/Resources/app.asar/node_modules/@joplin/lib/file-api-driver-webdav.js:166:21)

[laurent22]

@lethargosapatheia, could you try this please?

• In the settings, input a wrong password for you sync target
• Save and sync
• In the settings again, input the right password
• Save and sync

Does it work?

[lethargosapatheia]

It does work :) This is starting to look really good.

In my case I saw that the password was (seemingly) empty actually. After entering the actual password directly, it started working.

I don't remember exactly what it looked like in the intel-based version, but I'm guessing the passwords dots are there, just like there are dots now after entering the password.

So I guess something to catch the error now when the wrong password is entered would be great to have at some point, but I don't mind it as long as it works.

Actually, no, entering the wrong password explicitly does give out a somewhat better error:

Last error: Error: GET info.json: No public access to this resource., Username or password was incorrect, No 'Authorization: Bearer' header found. 

So it's only that initial stage which is weird.

Thank you, I'll continue to test it and see if anything weird pops up!

[vikingtoby]

Can confirm, download 2.12.7 on an M1, S3 sync did not work initially.

• Typed a random string in secret key
• Saved
• Typed the correct key
• Saved
• Everything works!

Thanks a lot! <3

[cablespaghetti]

Hi everyone, a new ARM64 release is available here: https://github.com/laurent22/joplin/releases/tag/v2.12.7

This is SO MUCH FASTER on my M1 Air. Thank you!

[laurent22]

Brilliant, thanks for confirming. What happens is that the new app is looking for the auth info in the wrong place in the keychain, so changing the password makes it save it back to the right place. But we indeed need to handle this better!

[ctoa]

Can confirm this is working great with Dropbox sync on M1 Macbook Pro!

[laurent22]

@ctoa, great! Did it work right away or did you also have issues with authentication initially?

[personalizedrefrigerator]

It does work :) This is starting to look really good.

In my case I saw that the password was (seemingly) empty actually. After entering the actual password directly, it started working.

I don't remember exactly what it looked like in the intel-based version, but I'm guessing the passwords dots are there, just like there are dots now after entering the password.

So I guess something to catch the error now when the wrong password is entered would be great to have at some point, but I don't mind it as long as it works.

Actually, no, entering the wrong password explicitly does give out a somewhat better error:

Last error: Error: GET info.json: No public access to this resource., Username or password was incorrect, No 'Authorization: Bearer' header found. 

So it's only that initial stage which is weird.

Thank you, I'll continue to test it and see if anything weird pops up!

@lethargosapatheia Could you please check whether there is a line containing KeychainService: could not set test password in Joplin's log? (To open the log file, click Help > Open Profile Directory, then open log.txt in a text editor). If such a line is present, Joplin may not be using the system's keychain (and may instead be storing the WebDAV password in plaintext).

[ctoa]

@ctoa, great! Did it work right away or did you also have issues with authentication initially?

It worked right away. Nothing needed to be done.

[boli]

working for me too - thanks @noah-nash and @laurent22

[laurent22]

@boli, nice to hear it works! What sync method do you use?

[boli]

@boli, nice to hear it works! What sync method do you use?

using webdav here.
i took the opportunity to upgrade auth on my webdav from 'simple pw' to ldap - so i cant tell you if i needed to reset the password or not - as my other changes necessitated a password change anyway.

[tthnu]

Nice work! It works very well when I entered the right password after entered some random characters and applied it. I use S3 as the sync method.@laurent22

[lethargosapatheia]

@personalizedrefrigerator
Hi,

I think this is all I get in relation to "KeyChainService":

2023-07-14 11:11:47: "KeychainService: checking if keychain supported"
2023-07-14 11:11:47: "KeychainService: check was already done - skipping. Supported:", "1"
2023-07-14 11:11:47: e2ee/utils: "Master password is not set - trying to get it from the active master key..."
2023-07-14 11:11:47: handleSyncStartupOperation: "Processing operation:", "0"
2023-07-14 11:11:47: App: "Client ID: 72bda5ca2d784296b60bde5060ab350f"
2023-07-14 11:11:47: models/Setting: "Applying default migrations..."
2023-07-14 11:11:47: e2ee/utils: "Trying to load 0 master keys..."

[gaffneyd4]

v2.12.7 works on my 2020 M1 13.4.1 OS macbook. First time install using arm64.dmg. Set up sync from scratch with s3 against minio backend works too. Thanks to those who helped troublehoot the arm errors to bring us a working version!

[gaffneyd4]

Downloading v2.12.7 was my first upgrade in awhile and after syncing I saw this error message on my other Joplin installations: "Some items cannot be decrypted." The solution to that problem was to upgrade my other Joplin installations, following the instructions in this post: https://discourse.joplinapp.org/t/if-you-have-an-issue-with-encryption-please-read-this/31552.

Just thought I'd pass along in case this saves someone else the google.

[predmijat]

I've installed 2.12.7 a few days ago and just noticed that I can no longer copy to system clipboard using the ViM mode ("+y).

[amandamcg]

Posting what I saw and how I got syncing to work since my case seemed slightly different than what's discussed above:

• Updated Mac to Joplin 2.12.7
• Noticed that I had a banner asking for a new master pass
• Instead of adding a new pass, I just filled in the old one that was there (but no longer filled in with ****)
• All seemed ok, but noticed that I was getting a cryptic sync message "2023-07-16 10:39:53: Synchronizer: "Error: GET info.json: Unknown error 2 (401): ..." (That lead me to this thread)
• I discovered this error was likely because my Webdav password was missing
• Readded the webdav password in settings
• Double checked syncing from iPhone to Mac and all is well.

(Haven't been active lately in forum, but I am still a happy Joplin user. Thanks as always for all of your hard work!)

[laurent22]

We now support M1 processors