Most active commenters

    ←back to thread

    255 points rd07 | 11 comments | | HN request time: 0.531s | source | bottom
    1. mosburger ◴[] No.41299442[source]
    Is anyone else getting a "“Pragtical.app” is damaged and can’t be opened. You should move it to the Trash" error when attempting to run the arm64 build on macOS? Really wanted to try it out!

    I suppose it could just be some security crap Corp IT installed on my laptop preventing it from installing.

    It looks like it's only taking up 7.9MB in my Applications folder so it must be corrupt or something.

    replies(5): >>41299462 #>>41299509 #>>41299668 #>>41299704 #>>41300440 #
    2. kccqzy ◴[] No.41299462[source]
    That sounds like a code signing error. 7.9MB is a good size.
    3. yas_hmaheshwari ◴[] No.41299509[source]
    I have seen a similar error in the past, and that one was because of MacOS extended permissions

    ``` cd /Applications/DBeaver.app/; ls -@l ```

    And then if you see some extended attributes like quarantine and provenance, you can remove them

    ``` xattr -d com.apple.provenance DBWeaver.app/; xattr -d com.apple.quarantine DBWeaver.app/ ```

    replies(1): >>41301613 #
    4. tunaoftheland ◴[] No.41299668[source]
    Haven't tried with Pragtical (hard to say it out loud BTW, lol) but have had success with right-click-opening other apps that give this error. Sometimes I need to do it multiple times to open it as normal. No issues with the apps themselves, has to do with app signing (or lack thereof for many macOS apps that one just downloads from a site).
    replies(1): >>41299808 #
    5. rpastuszak ◴[] No.41299704[source]
    FWIW the universal build works with the right mouse button click trick
    replies(1): >>41301408 #
    6. tom_ ◴[] No.41299808[source]
    An error about the app being damaged specifically can stem from the contents of the .app folder being modified after it was signed with the codesign tool. You can use codesign --verify (consult the man page) to get some info about why it's being considered damaged.

    I've got this wrong in the past by adding the README too late in the process. Once I'd fixed that, the reason macOS gives for not opening my app became that Apple can't check it for malicious software. Much better... I think? The right click/open workaround does work.

    7. hoistbypetard ◴[] No.41300440[source]
    I am also getting that error. I have no security crap from Corp IT on my personal macbook.
    8. tbeseda ◴[] No.41301408[source]
    FYI, in macOS v15 Sequoia +, Gatekeeper/quarantine/signing has changed. Right click to open won't allow the bypass. The quickest way, without disabling runtime protection:

    `xattr -r -d com.apple.quarantine /Applications/Pragtical.app`

    -d is delete -r is recursive

    Hopefully, Apple won't lock it down further.

    replies(1): >>41302821 #
    9. ◴[] No.41301613[source]
    10. bityard ◴[] No.41302821{3}[source]
    Hmm. That worked for me, but when I run the app, everything in it is reeeealy tiny. Like they're trying to work around Retina display scaling but got it wrong somehow.
    replies(1): >>41306242 #
    11. rd07 ◴[] No.41306242{4}[source]
    Have you tried changing the scale through Settings > Plugin > Scale ?