m1打不开，提示 “Another Redis Desktop Manager.app”已损坏，无法打开

[guziwen-lab]

OS

Mac

VERSION

1.5.2

ISSUE DESCRIPTION

下载m1-arm64版本打不开，提示“Another Redis Desktop Manager.app”已损坏，无法打开。 您应该推出磁盘映像。

[qishibo]

在修了，可能是升级工具导致的

[marchpane]

Hi!

I just did an update via Brew and now getting the same error. Can we do something to fix it?

Thank you

[qishibo]

@marchpane you can downgrade to v1.5.1 temporary, and I 'll fix it in 1.5.3 soon

[qishibo]

报错已损坏的先执行下面命令，之后就能使用了
if Mac M1 errors damaged and can’t be opened. You should move it to the Trash:

1. sudo xattr -rd com.apple.quarantine /Applications/Another\ Redis\ Desktop\ Manager.app
2. reopen it

[martijnhartlief]

I don't think disabling Gatekeeper is a good practice. Any timeline on a signed M1 release?

[qishibo]

I don't think disabling Gatekeeper is a good practice. Any timeline on a signed M1 release?

In processing, the previous certificate needs to be revoked. Apple has been reviewing it for nearly 20 days and has not made progress yet...

[uandco]

I don't think disabling Gatekeeper is a good practice. Any timeline on a signed M1 release?

Disabling Gatekeeper just to allow one application to run is indeed a terrible idea and should not be provided as a workaround. I'd rather use the Intel version than putting my whole system at risk. Or stick with 1.5.1 that somehow doesn't have that issue (funnily enough it's listed as an iOS app in System Report).

[marchpane]

Hi @uandco
I was also sceptical first as I'm more or less new to MacOS and whilst searching for explanations about these commands I found one article who said that you must/should turn it back after you made the changes.

1. sudo spctl --master-disable
2. sudo xattr -rd com.apple.quarantine /Applications/Another\ Redis\ Desktop\ Manager.app
3. sudo spctl --master-enable

I now understand the risk of it. A check could be done via spctl --status.

Now there is already 1.5.5 released and people should not forget to turn back their Gatekeeper settings in MacOS as the issue is resolved now.

[andrew-stclair]

This issue has returned in 1.6.1 on M1 mac

[qishibo]

This issue has returned in 1.6.1 on M1 mac

try #782 (comment)