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

    MacOS - A JavaScript error occurred in the main process

    General Discussion
    2
    8
    70
    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.
    • S
      Simon
      last edited by

      Hi Guys,
      Need some help with this error, please.
      Not a clue....
      Any ideas how to resolve, please?
      Appreciate the support, cheers,
      Simon

      Image 23-10-2025 at 09.00.png

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

        @Simon, did you do anything right before you got this message, like click something, create a new command, or disconnect your Internet? Can you reproduce the error at-will? Any info you have would help me reproduce it so I can easily figure out how to prevent it.

        Russell VanderMey

        S 1 Reply Last reply Reply Quote 0
        • S
          Simon @Russ
          last edited by

          @Russ Hi Russ, thanks for your response. No, didn't do anything...as such. Only recently installed, I run it, works spot on, absolutely great, as expected.... but, then I leave it running....come back and see this message. Seen it loads of times now (every time). Only happens after I leave it idle for a while... Hope you can help, because it's a great bit of software, thanks.

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

            @Simon, it just happened to me too. I have a bug in the 1.0.50 mac version. Sorry about that. I'm working on it now. Thank you for reporting it.

            EDIT: @Simon, I just posted a new mac version of the agent (1.0.51) that fixes this bug.

            Russell VanderMey

            S 3 Replies Last reply Reply Quote 0
            • S
              Simon @Russ
              last edited by

              @Russ Thanks Russ, really appreciate the support... you're a star 🙂 Will give it a go now.... Cheers, Simon

              1 Reply Last reply Reply Quote 1
              • S
                Simon @Russ
                last edited by

                @Russ Hi Russ, total fresh install using new release, but come back to it this morning, and found this error.... 😞 Help please... Image 26-10-2025 at 08.38.png

                1 Reply Last reply Reply Quote 0
                • S
                  Simon @Russ
                  last edited by

                  @Russ Hi Russ, I have removed everything, including Home Assistant integration. Re installed again, and seems better... at the moment.... will keep an eye on it. Really appreciate your support, thank you.

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

                    @Simon thanks again for reporting the error. I'll see if I can reproduce it. It looks like it's in the Home Assistant integration. Sorry about the trouble.

                    EDIT: I see from your screenshot that this.computer_name was null for some reason, so I added code to prevent a crash when that happens. I'll produce a new version soon.
                    https://github.com/rvmey/TRIGGERcmd-Agent/commit/b54e988e7d251105bc6faa8c3fa6a5240644cbef

                    EDIT2: Done - please upgrade to the current version (v1.0.52) to avoid that error in the future.

                    Russell VanderMey

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