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

macOS M1 chip install fail #3180

Closed
zjslqshqz opened this issue Apr 2, 2022 · 9 comments
Closed

macOS M1 chip install fail #3180

zjslqshqz opened this issue Apr 2, 2022 · 9 comments

Comments

@zjslqshqz
Copy link

The arm version cannot be opened after installation, and the x86 version can be used normally. do not know why.

Versions

@saowu
Copy link

saowu commented Apr 7, 2022

I also had the same problem

@YalandHong
Copy link

More info is needed. Please provide screenshot, video or describe how to reproduce your problem.


你的问题描述很不详细。请提供更多信息,比如截图、录屏或者具体操作的步骤。

@DanferWang
Copy link

image

Same error as mine. I used both .zip and .dmg file to install but they were failed.

@YalandHong
Copy link

image

Same error as mine. I used both .zip and .dmg file to install but they were failed.

Dup of #2983.

From Big Sur 11, macOS prevents you from running untrusted program. Any executable must be codesigned. I believe this issue should affect a lot of programs on macOS, not only MarkText.

@slaveofcode
Copy link

Same problem here on M1 Monterey 12.3.1

@FlorianLoch
Copy link

As mentioned, see #2983.

Just to also have this here: The binary isn't broken, it's just not signed. Run xattr -r -d com.apple.quarantine /Applications/MarkText.app to have macOS not put it in quarantine.

@Tangroo
Copy link

Tangroo commented Jun 30, 2022

I have the same problem,my macOS is Big Sur 11.2.3 and M1.
But the marktext-x64.dmg is available to me!

@FlorianLoch
Copy link

Everyone will have the same problem because it's nothing about your machine, it's about the binary not being signed.

For how to circumvent this please see the issue referenced by me above. :)

With x64 Apple applies different rules, that's why this one is working for you.

@fxha
Copy link
Contributor

fxha commented Jul 2, 2022

Thank you for reporting the issue. We noticed that this is a duplicate and closing it in favor of #2983. You may want to subscribe there for further updates.

@fxha fxha closed this as completed Jul 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants