🤖Have you ever tried Chat.M5Stack.com before asking??😎
    M5Stack Community
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    M5Burner on MacOs Sequoia 15.1 does not work

    UiFlow 2.0
    5
    5
    1.4k
    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.
    • B
      bobkummerfeld
      last edited by

      The MacOS M5Burner is prevented from running due to possible security problem.
      It is Intel code but my system is apple chip (M1).

      ajb2k3A 1 Reply Last reply Reply Quote 0
      • ajb2k3A
        ajb2k3 @bobkummerfeld
        last edited by

        @bobkummerfeld You need to grant permission to M5Burner to run.
        Apple changed the security to prevent none App Store apps from running and so you need to manually permit access.

        The process is a bit confusing so please google how to permit none approved apps from running on Apple M1 based computers.

        UIFlow, so easy an adult can learn it!
        If I don't know it, be patient!
        I've ether not learned it or am too drunk to remember it!
        Author of the WIP UIFlow Handbook!
        M5Black, Go, Stick, Core2, and so much more it cant be fit in here!

        1 Reply Last reply Reply Quote 0
        • aivarannamaaA
          aivarannamaa
          last edited by

          Run following command in Terminal:

          xattr -c /Applications/M5Burner.app

          This will remove the quarantine flags from the app.

          DINK74D H 2 Replies Last reply Reply Quote 2
          • DINK74D
            DINK74 @aivarannamaa
            last edited by

            @aivarannamaa I just ran into this issue, and your advice helped (MBA M2 Sequoia 15.2) – thank you!

            1 Reply Last reply Reply Quote 0
            • H
              haruhisa @aivarannamaa
              last edited by

              @aivarannamaa
              This solved the problem. Thanks!

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