Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

When I click 'show file content' of the executable file, I am shown a folder called 'contents', when opening that folder I get the folders '_CodeSignature', 'Frameworks', 'MacOS', 'MonoBleedingEdge' etc. In neither folder is a file that I can execute to open up the game.

Yeah, I think it's supposed to open the whole executable and not go into it and search for something to start there.

Well, not sure what else to try now, sorry about that. I'll let you know if I find something out and kindly ask you to please keep me updated if you come across a solution.

(+1)

Sure no problem! I think the problem indeed lays in the fact that MacOS can't find a file format or program to execute to start the game. I'll keep you updated if I find the solution. 

Keep me also updated if you find a solution. This could let a lot of games run on MacOS that now seem incompatible, despite having a Mac build.

I actually got it working, but it isn't plug and play!

Step 1: Open terminal

Step 2: type chmod +x 

Step 3: Drag the file you find in: "Left click on the game -> Show package contents -> MacOS" to the terminal and press ''enter''.

(!) Dont't use ''enter'' between the chmod +x command and the file you want to drag.

This will make the file an executable file, which makes it possible to boot up the game.

The problem is that the Mac doesn't recognise the executable file on default.

Great to hear that you got it working!

May I ask where you found this solution? Still trying to figure out if this is a general issue with Unity Mac builds or if it's something more specific...

A developer of another game gave me the solution. I have to say that with every Mac Unity game, let's say 10/20 games, I had to perform this solution every time.