jake rodriguez

I've got a standalone app I've built in 8.2.0 and running on a Mac Mini M1 processor. When i run the standalone on the mac mini, I get the security "app would like to use the microphone" prompt on every start of the application, despite my having granted it, and every change i make to the audio status also brings up this prompt. if i quit out of the standalone, and check security preferences, i can see my standalone has been granted access to the microphone, but it still prompts me every start and every driver change i make.

I've got a standalone app I've built in 8.2.0 and running on a Mac Mini M1 processor. When i run the standalone on the mac mini, I get the s

standalone-created-in-8-2-0-on-m1big-sur

Hey Jake! I can repro here and we will investigate. It just seems to be a problem on Big Sur (as far as I can tell).

hey Ben. yes--can confirm the security stuff is not an issue on my Mojave machine.

Hi, I think Big Sur tightens up security a bit more than Catalina and insists on a code-signed and properly entitled application for some types of persistent security permissions (like mic or camera). It's unclear from your post whether your app is signed/entitled with the "com.apple.security.device.audio-input" key set to true.

In case helpful, steps for code signing your standalone application are outlined here:

https://cycling74.com/articles/max-8-1-mac-os-10-15-catalina-support-and-notarization

In case helpful, steps for code signing your standalone application are outlined here:
https://cycling74.com/articles/max-8-1-mac-os-10-15-catalina-support-and-notarization

thanks pals for this help. it's been a minute since i've bundled to a standalone and didn't realize Apple had gotten so touchy. will attempt to code sign and try again.

thanks pals for this help. it's been a minute since i've bundled to a standalone and didn't realize Apple had gotten so touchy. will attempt to code sign and try again.
jk

I'm having issues distributing a standalone using a fork of an external (max-ble) which I compile myself.

I'm actually building the standalone on a 2015 macbook pro running catalina, and it doesn't work as expected on a recent M1 macbook running mac os 11, which of course I don't have access to.

I was still using Max 8.1.11 and everything worked fine except the scanning of BLE devices ([max-ble] seemed to work correctly but couldn't find any device), so I gave a try with Max 8.2.2 and apparently it doesn't even open any window anymore, except the console which doesn't display anything.

For information, I distribute the standalone by zipping it and uploading it to a public folder on my server.

Enabling the "rosetta" option on the standalone from the M1 apparently doesn't help in any case.

As suggested by Joshua, I tried to sign the standalone with the following Entitlements.plist file :

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<key>com.apple.security.device.bluetooth<;/key>

codesign -s <my_developer_id> --options runtime --timestamp --force --deep --entitlements ./Entitlements.plist -f <my_standalone_path>

But then when I open the standalone on my machine, no object is found, everything is red and I get a load of error messages in the console, which seems to indicate that my entitlements somehow override default entitlements applied during the standalone build process.

Any further hints on the use of an entitlements file to sign a standalone ?

Any other advice would be much appreciated too.

It looks like things were going better with Max 8.1.11 (and the standalone size was much smaller : 64 Mo with Max 8.1.11 compared to 235 Mo with Max 8.2.2), so meanwhile I'll give another try with it and double check with my standalone user if he didn't do anything that could have prevented BLE devices to be discoverable.

I'm having issues distributing a standalone using a fork of an external (max-ble) which I compile myself.
I'm actually building the standalone on a 2015 macbook pro running catalina, and it doesn't work as expected on a recent M1 macbook running mac os 11, which of course I don't have access to.
I was still using Max 8.1.11 and everything worked fine except the scanning of BLE devices ([max-ble] seemed to work correctly but couldn't find any device), so I gave a try with Max 8.2.2 and apparently it doesn't even open any window anymore, except the console which doesn't display anything.
For information, I distribute the standalone by zipping it and uploading it to a public folder on my server.

As suggested by Joshua, I tried to sign the standalone with the following Entitlements.plist file :
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>com.apple.security.device.bluetooth<;/key>
    <true/>
</dict>
</plist>

using the following command line :
codesign -s <my_developer_id> --options runtime --timestamp --force --deep --entitlements ./Entitlements.plist -f <my_standalone_path>

But then when I open the standalone on my machine, no object is found, everything is red and I get a load of error messages in the console, which seems to indicate that my entitlements somehow override default entitlements applied during the standalone build process.
Any further hints on the use of an entitlements file to sign a standalone ?
Any other advice would be much appreciated too.

It looks like things were going better with Max 8.1.11 (and the standalone size was much smaller : 64 Mo with Max 8.1.11 compared to 235 Mo with Max 8.2.2), so meanwhile I'll give another try with it and double check with my standalone user if he didn't do anything that could have prevented BLE devices to be discoverable.

Any news or solutions for this problem? I encounter this problem with Max 8.6.2 and MacOS Monterrey 12.6.1.

standalone created in 8.2.0 on M1/Big Sur