New restrictions on Mac OS for exported apps?

Not favoritedFavorited Favorited 0 favourites
  • 4 posts
From the Asset Store
Royal Panda Casino
$40 USD
60% off
Create your own casino app and import it to Google Play and the App Store.
  • Hi

    I am used to exporting games to my mac, then right-clicking to open the app, then going in to settings to allow the app to run in 'Privacy & Settings'.

    But this is not working at all now in the latest version of Mac OS (M4 Mac mini Pro) and so its impossible to test a game on Mac.

    I am having to pay $100py now for an Apple Developer account, just so I can test an exported Mac game.

    This is obviously not a Scirra issue, but very annoying nonethless.

    Has anyone managed to get around this?

    Tagged:

  • OK, this may help someone out there on Macs. This has definitely changed since I last exported a game on a Mac.

    Do this:

    1. place the [gamename].app file into your Applications folder

    2. Right-Click your [gamename].app file and select Open (and follow any prompts)

    3. Go to System Settings > Privacy > Allow app to run.

    You will still not be able to run it at this point...but if then you go to a terminal and type the following, you will then be able to run it:

    codesign --force --deep --sign - /Applications/[gamename].app

    This is longwinded just for a test, but its now necessary for testing a Mac export.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • Good that you posted the answer!

    I'm only using the browser for testing now, because I haven't noticed any difference in my projects.

  • Our guide on exporting to macOS should be up-to-date for the latest macOS versions. I just checked it with the latest macOS 15.4.1 though, and it does seem like macOS has made it even harder to run unsigned apps. The previous documented process of running sign-adhoc.command before running the app still works, but now in both cases it blocks running the script or app with a security warning. However if you open Settings and go to the Privacy & Security section and scroll to the bottom, there is an 'Open anyway' button you can use to bypass the security warning.

    You can also use the terminal to run sign-adhoc.command which appears to bypass the security warning, but this does not appear to work for running the app itself.

    I've updated the guide on exporting to macOS to cover these additional steps.

Jump to:
Active Users
There are 0 visitors browsing this topic (0 users and 0 guests)