Standalone Mac permissions launch problem

    MaxMSPadvancedbugs/issues

    jb@bmbcon.demon.nl
    Jan 22 2022 | 2:28 pm
    Hi there, I have a Mac standalone made with Max 8.2.0 which uses an audio input (actually from loopback) and an external USB camera (to trigger things).
    It's working fine. But as it needs to run for a long time (months) in an installation, I would like to launch it automatically when the computer starts up (as a Login item). This works, but during the startup process, dialog boxes appear asking for permission for "... MSP to capture audio from the microphone." and to "Allow Jitter to capture video". Which need to be clicked on. I thought that the computer (mac mini running 10.13.4) would learn that it's ok for the app to do this (it appears in and stays in the relevant lists in the Security control panel). but these dialogs appear EVERY TIME.
    Launching the standalone app on my laptop (OS 12.1) displays the same behaviour, so I don't think it's just an OS thing.
    I've done this kind of thing before and can't remember ever having this problem.
    can anyone help?
    very best wishes, Justin

    • tdc's icon
      tdc
      Jan 28 2022 | 2:50 am
      Interested in resolving this permissions issue also.
      Share
    • jb@bmbcon.demon.nl's icon
      jb@bmbcon.demon.nl's icon
      jb@bmbcon.demon.nl
      Jan 28 2022 | 8:41 am
      Actually I'm talking to support about it now.
      Going back to Max 8.1.11 and making the standalone with that version solves the problem, - i only have to give permission once, then the computer remembers the permissions. so it seems to be a bug in the newer version(s). I'll post here again when I have more news about it! J
    • personal_username's icon
      personal_username's icon
      personal_username
      Jan 29 2022 | 9:53 am
      Hi Justine,
      if I recall correctly you can bypass this with an apple developer ID. Once you have one, you should codesign* the app with a script.
      Check this thread: https://stackoverflow.com/questions/13204407/how-to-codesign-an-existing-mac-os-x-app-file-for-gatekeeper
    • jb@bmbcon.demon.nl's icon
      jb@bmbcon.demon.nl's icon
      jb@bmbcon.demon.nl
      Jan 29 2022 | 11:55 am
      Thanks for the link! I'll check it out. It all seems to work anyway by using Max 8.1.11. And hopefully the bug will be fixed in a future version of Max.
    • Carlos Caires's icon
      Carlos Caires's icon
      Carlos Caires
      Feb 21 2023 | 12:47 pm
      Same here. I'm forced to export my App (https://irin.carloscaires.com/ ) using max 8.1.11. Did anyone reported this issue in the bug report form?
    • CharBoogie's icon
      CharBoogie's icon
      CharBoogie
      Jun 06 2023 | 12:39 pm
      Anybody have any news on this? I can't even find where to download Max 8.1.11 anymore! Seems the oldest avail on the website is 8.2 something...
    • Source Audio's icon
      Source Audio's icon
      Source Audio
      Jun 06 2023 | 2:53 pm
      Max 8.1.11. is surelly still available for download, but link is not shown is this for your own needs? in which case you could get rid of stupid apple security restrictions. if you think solution is to use 8.1.11 I could digg download link from archives
    • Source Audio's icon
      Source Audio's icon
      Source Audio
      Jun 06 2023 | 3:33 pm
      https://akiaj5esl75o5wbdcv2a-maxmspjitter.s3.amazonaws.com/Max8111_210413.dmg
    • Francois Weber's icon
      Francois Weber's icon
      Francois Weber
      Jun 07 2023 | 1:08 pm
      Hi all, Same thing with my standalone... but i can't use the 8.1.11 because of some objects that have since been updated (ex : mc.resize). I hope C74 solves this problem in the next release...
    • Rob Ramirez's icon
      Rob Ramirez's icon
      Rob Ramirez
      Jun 07 2023 | 1:15 pm
      You simply need to codesign the standalone app bundle. From a terminal:
      codesign -s - -f mystandalone.app
    • Francois Weber's icon
      Francois Weber's icon
      Francois Weber
      Jun 08 2023 | 8:11 am
      Hi Rob,
      Thank you for your reply. I did that, but unfortunately it doesn't work. I get the following error message in the terminal : " resource fork, Finder information, or similar detritus not allowed "
    • billyanok's icon
      billyanok's icon
      billyanok
      Jun 08 2023 | 8:30 am
      Run first before codesign
      sudo xattr -cr mystandalone.app
    • CharBoogie's icon
      CharBoogie's icon
      CharBoogie
      Jun 08 2023 | 11:55 am
      Thank you everyone for your replies!
      I'm having the same issue now -- realizing that I need the functionality of some updates since 8.1.1.
      I thought that you needed to register an Apple developer ID in order to co-design the app?
    • billyanok's icon
      billyanok's icon
      billyanok
      Jun 08 2023 | 4:49 pm
      Yes you do as far as I know? B
    • Rob Ramirez's icon
      Rob Ramirez's icon
      Rob Ramirez
      Jun 09 2023 | 12:31 am
      you don't need a developer ID when you sign anonymously, which is what passing "-" to the "-s" flag does
    • Francois Weber's icon
      Francois Weber's icon
      Francois Weber
      Jun 09 2023 | 10:31 am
      Thanks Rob, Thanks Billyanok !!!!
      I did :
      sudo xattr -cr mystandalone.app then
      codesign -s - -f mystandalone.app
      And all is right now, without Apple developer ID.
    • billyanok's icon
      billyanok's icon
      billyanok
      Jun 09 2023 | 1:33 pm
      No problem, glad to help!
      @Rob Ramirez - interesting, I didn't know this- "you don't need a developer ID when you sign anonymously, which is what passing "-" to the "-s" flag does"
      B
    • CharBoogie's icon
      CharBoogie's icon
      CharBoogie
      Jun 10 2023 | 9:56 am
      Amazing! Going to give it a shot... thanks everyone!
    • Martin.Jirsak's icon
      Martin.Jirsak's icon
      Martin.Jirsak
      Jun 13 2023 | 9:29 am
      Hi all,
      I have an issue, which might be related (or not, I don't know).
      I tried to use mxj_autobot and/or 11clicks externals. Everything works as expected until I export my patch as stand-alone application on Mac. In the exported stand-alone the mouse movement doesn't work anymore. My expectation is, I have to enable the application in the System Settings > Privacy & Security > Accessibility on macOS. But even if I do so, the mouse doesn't move.
      Max is also enabled in the Accessibility and both the externals work within Max.
      Do you have any idea, please? Do I have to setup something specific in the [standalone] object or on the export, so the system recognizes the new application correctly? Or any other idea, please?
      I tried to use the Terminal tricks, you recommended, but it didn't help.
      Thank you for any hint!