Issue opening Unity Mac applications on Mac Big Sur OS from Unidentified Developer

We are Windows PC Unity users and have built Mac applications for our Mac users for a number of years. Our Mac users have never had any issue opening the Mac builds we generated although sometimes they would have to change the security settings to give permission to open the Mac viewer from an Unidentified developer.

However this security setting option appears to be absent in the latest Mac OS update call Big Sur, even though the advice on the Apple Technical Support page appears to say that Mac users can still open applications from unidentified developers;

https://support.apple.com/en-ie/guide/mac-help/mh40616/mac

Our clients have tried these instructions and still get an error message saying;
"You do not have permission to open this application"
Then advising them to contact their system administrators. System administrators have looked at this and cannot find a solution.

Has anyone here had this problem and if so, how did you overcome it?

 

I'm experiencing a similar issue, but I can't seem to find a place to make those changes. What file exactly are you opening to add the executable bit and remove the quarantine attributes?

 

Ah, I see. So there's no way to do this from a Windows PC?

 

I tried it with Ubuntu, and no luck.

 

No, chmod worked, but the xattr command didn't have an -r switch. (I think that means recurse through the directory?).
Anyway, someone trying to install my game on Big Sur had the same issue after I ran those commands on Ubuntu. It could be because I compressed the files afterward using file explorer though. Do you know if I would have to run compression from Ubuntu in order to maintain the executable bit data?

 

I'll give that a try and get back to you, thanks!

 

This video describes the procedure to solve this problem:-

YOUTUBE VIDEO TO DESCRIBE THE PROCEDURE



(SOLVED) "you do not have permission to open the application" only 3 steps to open apps on big sur

 

Yeah, I really don't see the issue if you're already running macOS, you can just mess with the files in the terminal. But, with a windows machine, you need to somehow add the executable bits with a WSL and move the build off the PC without letting File Explorer touch it.

 

I'm seeing builds done in 2020.2 on mac refuse to open in Big Sur - but rather than complaining about unknown developer - they say the app is damaged. Removing the quarantine flag fixes this. However - if someone is downloading the app - presumably BS will add the quarantine to the download - so how do you get an app to someone running BS without them having to do the remove quarantine thing?

 

Still getting this on 2020.3.0f1

 

I see this kind of message:

 

The output:

invalid Info.plist (plist or signature have been modified)
In architecture: x86_64

 

No

 

Bug report: (Case 1323501) macOS build reports as "Damaged" when downloaded from internet

 

For what it's worth - 2020.3 .0f1 fixes it for me so far.

 

Thank you Tautvydas

 

Thank you for this workaround. Unfortunately this doesn't seem to work in this case:

codesign -s - -f --deep /path/to/game.app

game.app: replacing existing signature
/Library/Developer/CommandLineTools/usr/bin/codesign_allocate: file not in an order that can be processed (code signature data out of place):
/path/to/game.app/Contents/PlugIns/FileBrowser.bundle/Contents/MacOS/FileBrowser
game.app: the codesign_allocate helper tool cannot be found or used
In subcomponent: /path/to/game.app/Contents/PlugIns/FileBrowser.bundle

 

Thanks for this idea!
The creator of the plugin has updated it to avoid this problem: https://forum.unity.com/threads/file-browser-native-file-browser.510403/page-7#post-6970496

 

Thank you! This worked, just wanted to note that you do not need to remove quartine attributes for 2019, pretty sure they only added that in 2020 version.

 

open terminal past "sudo chmod -R 755 " drag app on terminal and validate. type your password. launch (don't put in trash ) go security in setting and validate for open app.

if always problem after this, go terminal (sometimes problem with quarantine too)

"xattr -dr http://com.apple.quarantine " and drag the app and validate

(this resole problem for all unity app not build with macOS with my MacBook Pro M1)

 

Hi, bumping this issue: is the Big Sur quarantine thing fixed when creating MacOS builds on 2020 LTS ? Are there plans to fix it also on 2019 LTS ? (we still use that version for some projects)

 

Well I am not sure that I understand the problem correctly, then. I have built a macos app in Unity 2019.4.31 (on Windows), sent it to someone through transfernow.net to use on Big Sur, and he does have to go through the hassle of using command lines to fix it and run it.

Am I missing something ?
Is there a proper way to build it to prevent this problem ?

If I understand correctly, I have two options:
- build from mac (I am assuming I won't have the problem at all)
- build from PC, send it to a mac, run the two command lines once. After that I can send the app to anyone and they won't have to go through the process to run it

Is this correct ?