macOS Malicious Software Popup

After updating Joplin today via Homebrew. I received the infamous “Malicious Software” Popup. I know how to fix it,.

But why Joplin isn’t an registered with Apple App to prevent such pop-ups!?


If you are using Joplin I guess you trust it and what Apple thinks is pointless. If you have Windows 10 you have no doubt seen similar warnings which actually don’t give you any security. As long as you know what you are doing such forms of security have no meaning. These warnings are really designed to protect clueless users.

1 Like

I’m going to go on a limb and assume that much of it has to do with Apple’s development licenses. Even though Joplin is an open source project, to get an app on the Apple Store costs a yearly fee of $99 (usd) which is probably outside the budget.

1 Like

Another thing to consider: to be able to release an app on the Apple Store, every team member involved with that side of the project would need to own Mac’s. Those are also pretty pricey and second hand ones, despite being cheaper most of the time, they have the problem of not being compatible with the latest tools and libraries required.

1 Like

Tbh, Mac’s are not really suited for open source devel. It’s great for creatives, regular office usage and also iOS development but causes a good amount of grief while doing anything beyond that.
I have been programming for ten years now, changing over to Linux two years ago and I have never regretted that decision

I think it’s not user friendly and scaring away potential users of the app. Yes there is a yearly fee, but there is already an iOS App, so some of the developers must already have an Apple developer license. Donations could be setup to cover those kind of cost for a project like this.

@Drallas, Joplin does take donations. You’d have to talk to Laurent, since it’s his project. He may be interested if you’re willing to donate the license fee for it; not my call, though.

Laurent has a dev account and the app is signed. But Catalina requires notarization, and the notarization process does not fit the CI pipeline. So please complain to Apple for their new scam to dominate which apps to allow.


Thanks for the answer, @tessus. I didn’t have a clue about that but it makes sense.

@Drallas, if this is an issue for you and you only have Apple products, Bear is a great alternative that isn’t open source but has a highly active developer, costs $15 a year to use, and has better iOS integration than Joplin due to its exclusive focus on Apple products. Joplin isn’t for everyone and no one here expects you to only use it.

This problem is made worse with the fact that Catalina is such an awful release. I can’t upgrade because if I do I’ll lose Photoshop CS6, which is a 32-bit app. I’ll lose that and I’ll get… nothing in return. Well at best nothing and at worse some new bugs.

And so it means I can’t test anything on this OS. I’d like to fix the app actually but we might get stuck in this situation for a while, unless someone with the OS is ready to spend quite a lot time getting it to work.

Also as tessus mentioned, last we checked the notarisation process would not work on CI.



Photoshop cs6 was only 64 bit for mac when i had a copy

Unfortunately it definitely doesn’t work on Catalina:

1 Like

Fair point. That makes sense then. If you can get CC from donations, would it be worth upgrading then?

I can’t agree more. I still haven’t upgraded to Catalina because it’s such a bad release.

They changed even stuff without proper documentation. Now some of the preference pane apps don’t work anymore and noone knows why. (No errors/warnings during compile and/or runtime - they just don’t work.)

1 Like

@bedwardly-down As i stated it’s not an issue for me, but it’s inconvenient. btw I use Joplin only for my work related notes, syncing it to a local folder that has Gitlab upstream. I also maintain a personal knowledge base using some spaces on syncing to Github.

1 Like

@Drallas, sorry for the misinterpretation. That wasn’t stated in the original post or any other replies posted in this topic.

@laurent is Travis the CI system in question here? (just curious)

Yes, for macOS releases we use Travis.