TRIGGERcmd
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Crashing & translocation & ARM

    Mac
    2
    7
    172
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • G
      gajahduduk
      last edited by gajahduduk

      Hi. Just trying this for first time.

      The agent, installed in /Applications/ launches but has now crashed twice when editing commands.

      Also it appears to be running in translocation mode. According to LittleSnitch:

      "The application is running in App Translocation, a macOS security mechanism for apps that are not properly installed. You cannot create permanent rules until you move the application to the Applications folder and launch it from there."

      It is actually running from:

      /private/var/folders/*/TRIGGERcmdAgent.app/Contents/MacOS/TRIGGERcmdAgent

      Also:
      • any chance of an ARM build?
      • how bout option to make the menu bar icon a more standard black & white, with a dark mode?

      RussR 1 Reply Last reply Reply Quote 0
      • G gajahduduk referenced this topic on
      • RussR
        Russ @gajahduduk
        last edited by

        @gajahduduk, thanks. I'll look into an arm build and the icon change. Not sure why it's crashing. I'm pretty sure I tested it on an M1 arm mac.

        Russell VanderMey

        G 1 Reply Last reply Reply Quote 0
        • G
          gajahduduk @Russ
          last edited by

          @Russ thanks. pls check into translocation too.

          Here's a crash log from just now.

          RussR 2 Replies Last reply Reply Quote 0
          • RussR
            Russ @gajahduduk
            last edited by

            @gajahduduk, thanks. Researching this now.

            Russell VanderMey

            1 Reply Last reply Reply Quote 0
            • RussR
              Russ @gajahduduk
              last edited by Russ

              @gajahduduk, I built this amd64 (Apple Silicon) version. Would you mind testing it?

              https://agents.triggercmd.com/TRIGGERcmdAgent-arm64.dmg

              Russell VanderMey

              G 1 Reply Last reply Reply Quote 0
              • G
                gajahduduk @Russ
                last edited by gajahduduk

                @Russ Hi. Thank you for attempting this. Sorry I had no email notifications turned on, so didn't get this until today.

                Just tried it, there seem to be gatekeeper issues.

                alt text

                normally I can bypass this with a terminal command called xattr. However in this case even that doesn't work.

                usually this has to do with lack of code signing the executable.

                i reinstalled the x64 version and got this, which is expected, and after confirming it launched. note that I did not need to use xattr on this one, but maybe I had previously?

                (Prior to this, today, while adding some new actions, it crashed more than once.)

                alt text

                RussR 1 Reply Last reply Reply Quote 0
                • RussR
                  Russ @gajahduduk
                  last edited by Russ

                  @gajahduduk, thank you for testing it.

                  What MacOS version do you have? I suspect it's v15 (aka Sequoia) because they've made it a little harder to run apps like this.

                  Fortunately you can work around it with these steps:

                  1. Try to run TRIGGERcmdAgent, and click Cancel.
                  2. Open Security and Privacy in Settings.
                  3. Scroll down and click Open Anyway next to TRIGGERcmdAgent.

                  8d330481-1ff6-4f91-a1d8-db92c81036ad-image.png

                  Russell VanderMey

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post