Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mac issues #44

Open
nclm opened this issue Dec 20, 2024 · 9 comments
Open

Mac issues #44

nclm opened this issue Dec 20, 2024 · 9 comments
Labels
macOS Issue related to macOS

Comments

@nclm
Copy link

nclm commented Dec 20, 2024

On macOS 15.0.1 on a M1 Max:

Penpot-Desktop-0.7.0-arm64-mac doesn’t launch. Instead the error “Penpot Desktop.app” is damaged and can’t be opened. You should move it to the Bin. is displayed.

Screenshot 2024-12-20 at 11 44 08

Penpot-Desktop-0.7.0-mac does launch. But it’s very slow to load. It takes about 30 seconds before displaying a nearly empty window (only one tab). Then about 30 seconds more before displaying the UI in the window.

Screenshot 2024-12-20 at 11 42 58
@nclm nclm changed the title Two issues on mac. Mac issues Dec 20, 2024
@Belar
Copy link
Contributor

Belar commented Dec 21, 2024

Hi @nclm,
the warning about an application (in this case Penpot Desktop) being damaged is how Apple treats an app that hasn’t been signed through their Developer program. I do intend to sign Penpot Desktop, but the requirements are demanding from an open source project’s perspective.

There is a way to bypass the blocker, but I don’t document it. Since it’s related to security, I believe everyone should do their own research - a workaround is easy to find.

The other issue (with the x64 installer) I suspect is a matter of an incompatible architecture, running x64 (Intel mac) on arm64 (Apple Silicon). That’s why it somewhat works, but with degraded performance.

@Belar Belar added the macOS Issue related to macOS label Dec 21, 2024
@MIfeanyi
Copy link

I don't beleive this issue is your typical unsigned issue due to the fact that it's stating that the app is damaged not untrusted. I could be wrong.

@Belar
Copy link
Contributor

Belar commented Dec 28, 2024

Hey, @MIfeanyi. The phrasing is unfortunate, in the case of an unsigned app, but this error is a well documented problem. While it can mean other issues, the chances are really low here.

@Beryesa
Copy link
Contributor

Beryesa commented Jan 25, 2025

@ericwaetke
Copy link

ericwaetke commented Feb 4, 2025

I’ve installed my fair share of unsigned apps on MacOS – never had the error, that the app “is damaged and can’t be opened” though.

When opening the package content and then executing the Unix Executable File, I have to go through the usual Privacy hoops, just to have the App crash right after.

Never worked on an MacOS/Electron App before, so if you know where I can find crash dumps to share let me know!

Edit: this indeed seems to be an issue with the arm version only. I can open the x86 version, though the performance is terrible and I get stuck in this state

Image

@ericwaetke
Copy link

Also, we @wovendesign have an Apple Developer Account and would offer to publish/sign the App, if the penpot team and everyone involved would be okay with that

@Belar
Copy link
Contributor

Belar commented Feb 7, 2025

Hi @ericwaetke,
I believe you. When researching the error, I saw different reports on whether an unsigned app works or not. The same with ways of running an unsigned app. It seems to differ between combinations of architecture (Apple Silicon, Intel), macOS version, and build. For example, the officially documented solution for running an unsigned app, through security settings, is not available on M1 and macOS 15.1.

I use the ARM installer myself and also test it in a VM with a default installation. The “X is damaged and can’t be opened.” error is fully reproducible, and clearing the app from quarantine (through xattr) allows it to run as expected.

if you know where I can find crash dumps

You could capture output (standard and error) through the open command. Here are the instructions.

The inconsistency with the treatment and lack of a clear message in case of an unsigned app are the main reasons why signing is necessary to reliably judge issues with the macOS version.
The good news is, we are in the process of getting the app signed. However, thank you very much for the offer; it means a lot that the project could receive that level of support.

@Belar Belar pinned this issue Feb 7, 2025
@ericwaetke
Copy link

Oh you are totally right! Turns out I was not correctly signing with xattr

The app does work indeed flawlessly!
But awesome news that you are in the process of signing the app :)

@Belar
Copy link
Contributor

Belar commented Feb 16, 2025

That’s great, thank you for the double-check @ericwaetke.
Yes, I’m looking forward to everyone on macOS enjoying a hassle-free installation and automatic updates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
macOS Issue related to macOS
Projects
None yet
Development

No branches or pull requests

5 participants