# Ignition on MAC - installer can't be opened because Apple can't check it

**URL:** <https://forum.inductiveautomation.com/t/ignition-on-mac-installer-cant-be-opened-because-apple-cant-check-it/71976>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [April 3, 2023, 3:35pm UTC](https://forum.inductiveautomation.com/t/ignition-on-mac-installer-cant-be-opened-because-apple-cant-check-it/71976 "2023-04-03T15:35:45Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![karl1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/karl1/32/51171_2.png) [@karl1](https://forum.inductiveautomation.com/u/karl1)\
**Post date:** [April 3, 2023, 3:35pm UTC](https://forum.inductiveautomation.com/t/ignition-on-mac-installer-cant-be-opened-because-apple-cant-check-it/71976/1 "2023-04-03T15:35:45Z")

</div>

This issue has been going on for a very long time, and it is mind boggling to me (in addition to be exceedingly frustrating) that this issue has not yet been resolved.

No one runs Ignition on MACs? Makes no sense to me. Maybe I'm just ignorant of something. Can someone enlighten me?

(I don't want hacks to get around this - we should haven't to play games like that).

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [April 3, 2023, 3:37pm UTC](https://forum.inductiveautomation.com/t/ignition-on-mac-installer-cant-be-opened-because-apple-cant-check-it/71976/2 "2023-04-03T15:37:37Z")

</div>

> [@karl1](#):
>
> No one runs Ignition on MACs?

> [@karl1](#):
>
> Can someone enlighten me?

Only for local development. Sometimes a Gateway, usually just a Designer. Nobody deploys to prod on a Mac.

Notarizing the installer is hopefully coming soon-ish.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [April 3, 2023, 3:41pm UTC](https://forum.inductiveautomation.com/t/ignition-on-mac-installer-cant-be-opened-because-apple-cant-check-it/71976/3 "2023-04-03T15:41:03Z")

</div>

Also, FWIW, when I need to run Ignition on my Mac I just use the zip distributions. They can be started/stopped by `ignition.sh start` or `ignition.sh stop`, and I think because I have Terminal.app set up as a developer tool in the security settings I never have any issues running it.

 ![Screenshot 2023-04-03 at 8.40.54 AM](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/6/56488b1c15d56c893de453652427a9fbe971e889.jpeg)

---

<div class="post-metadata">

**Author:** ![WillMT10](https://avatars.discourse-cdn.com/v4/letter/w/7feea3/32.png) [@WillMT10](https://forum.inductiveautomation.com/u/WillMT10)\
**Post date:** [April 3, 2023, 3:41pm UTC](https://forum.inductiveautomation.com/t/ignition-on-mac-installer-cant-be-opened-because-apple-cant-check-it/71976/4 "2023-04-03T15:41:39Z")

</div>

> [@Kevin.Herron](#):
>
> Nobody deploys to prod on a Mac.

🙋‍♂️ 😬 (On a limited basis with Mac Mini's)

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [April 3, 2023, 3:42pm UTC](https://forum.inductiveautomation.com/t/ignition-on-mac-installer-cant-be-opened-because-apple-cant-check-it/71976/5 "2023-04-03T15:42:38Z")

</div>

Whhhhhyyyyyyyy?

(and I ask this as a Mac user)

---

<div class="post-metadata">

**Author:** ![WillMT10](https://avatars.discourse-cdn.com/v4/letter/w/7feea3/32.png) [@WillMT10](https://forum.inductiveautomation.com/u/WillMT10)\
**Post date:** [April 3, 2023, 3:45pm UTC](https://forum.inductiveautomation.com/t/ignition-on-mac-installer-cant-be-opened-because-apple-cant-check-it/71976/6 "2023-04-03T15:45:26Z")

</div>

Small locations. Usually have a Mac Mini as a shelf spare. Plus only recently built out a dedicated IT team. Gave more peace of mind from a security standpoint when dealing with limited resources to monitor hardware. Windows drives me crazy and not quite comfortable enough with Linux to not waste many hours when having to maintain an asset.

(Fully agree it is a fair question though 😅)

---

<div class="post-metadata">

**Author:** ![mathieurleblanc33](https://avatars.discourse-cdn.com/v4/letter/m/e19adc/32.png) [@mathieurleblanc33](https://forum.inductiveautomation.com/u/mathieurleblanc33)\
**Post date:** [April 3, 2023, 3:46pm UTC](https://forum.inductiveautomation.com/t/ignition-on-mac-installer-cant-be-opened-because-apple-cant-check-it/71976/7 "2023-04-03T15:46:54Z")

</div>

I have Ignition 8.1.23 currently running on 2012 Mac Server.  
I had minor issues installing Ignition but I think it was me as new user to Mac. We run designer on Mac.  
Check this link:

> [@Installing Ignition on macOS - Monterey - Gateway Installer doesn't launch](https://forum.inductiveautomation.com/t/installing-ignition-on-macos-monterey-gateway-installer-doesnt-launch/67161/4):
>
> Hi, Thank you for your input. It seems like your workaround did work for me. I was able to install Ignition on macOS.

It may help.

---

<div class="post-metadata">

**Author:** ![karl1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/karl1/32/51171_2.png) [@karl1](https://forum.inductiveautomation.com/u/karl1)\
**Post date:** [April 3, 2023, 3:58pm UTC](https://forum.inductiveautomation.com/t/ignition-on-mac-installer-cant-be-opened-because-apple-cant-check-it/71976/8 "2023-04-03T15:58:55Z")

</div>

I’m doing development. I have MACs, don’t want to deploy a VM or spend the $$ on a Windows license just to run something that is supposed to run on a Mac.

---

<div class="post-metadata">

**Author:** ![karl1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/karl1/32/51171_2.png) [@karl1](https://forum.inductiveautomation.com/u/karl1)\
**Post date:** [April 3, 2023, 3:59pm UTC](https://forum.inductiveautomation.com/t/ignition-on-mac-installer-cant-be-opened-because-apple-cant-check-it/71976/9 "2023-04-03T15:59:37Z")

</div>

(But more importantly: how difficult can this be – get it configured and setup with Apple if you’re going to offer a MacOS compatible version.)

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [April 3, 2023, 4:04pm UTC](https://forum.inductiveautomation.com/t/ignition-on-mac-installer-cant-be-opened-because-apple-cant-check-it/71976/10 "2023-04-03T16:04:31Z")

</div>

> [@karl1](#):
>
> don’t want to deploy a VM

How do you match your end-user environment or otherwise ensure what you are doing will run properly? Writing off VMs so blithely strikes me as [self-redacted], IMNSHO.

---

<div class="post-metadata">

**Author:** ![karl1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/karl1/32/51171_2.png) [@karl1](https://forum.inductiveautomation.com/u/karl1)\
**Post date:** [April 3, 2023, 4:22pm UTC](https://forum.inductiveautomation.com/t/ignition-on-mac-installer-cant-be-opened-because-apple-cant-check-it/71976/11 "2023-04-03T16:22:09Z")

</div>

I’m developing in a lab. If I had a real world target, that would be different.

The point is: why not fix the installation problem if you have a version for deployment in that environment. The point is **not** what my environment is and why I use it.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [April 3, 2023, 4:27pm UTC](https://forum.inductiveautomation.com/t/ignition-on-mac-installer-cant-be-opened-because-apple-cant-check-it/71976/12 "2023-04-03T16:27:17Z")

</div>

> [@karl1](#):
>
> The point is: why not fix the installation problem if you have a version for deployment in that environment.

I agree it should be fixed. We have an open issue for it. It's even got a Q2 target on it now.

The simple truth, though, is that this issue is, and has been, lower priority than other work this team is responsible for. Mac is not a priority.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [April 3, 2023, 4:34pm UTC](https://forum.inductiveautomation.com/t/ignition-on-mac-installer-cant-be-opened-because-apple-cant-check-it/71976/13 "2023-04-03T16:34:50Z")

</div>

> [@karl1](#):
>
> The point is **not** what my environment is and why I use it.

As you say above:

> [@karl1](#):
>
> we should haven't to play games

Apple places extra roadblocks in the way of software distribution. Presumably to protect their userbase (from themselves), but, in my opinion, more to protect their walled garden. Regardless of justification, it is a roadblock that will cause multi-platform products to lag on Macs. Unless you are willing to work around the restrictions (aka "hack").

I think your criticism of IA is unjust--you should be complaining to Apple.

---

<div class="post-metadata">

**Author:** ![karl1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/karl1/32/51171_2.png) [@karl1](https://forum.inductiveautomation.com/u/karl1)\
**Post date:** [April 3, 2023, 4:47pm UTC](https://forum.inductiveautomation.com/t/ignition-on-mac-installer-cant-be-opened-because-apple-cant-check-it/71976/14 "2023-04-03T16:47:36Z")

</div>

… or there should be some warning or something because it’s a tough wall to run into when you think you just need to download and install.

That said, your point is fair.

---

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [April 5, 2023, 12:24am UTC](https://forum.inductiveautomation.com/t/ignition-on-mac-installer-cant-be-opened-because-apple-cant-check-it/71976/15 "2023-04-05T00:24:53Z")

</div>

> [@pturmel](#):
>
> Presumably to protect their userbase (from themselves)

😂 this made me lol, very true

---

<div class="post-metadata">

**Author:** ![BalaDBX](https://avatars.discourse-cdn.com/v4/letter/b/f475e1/32.png) [@BalaDBX](https://forum.inductiveautomation.com/u/BalaDBX)\
**Post date:** [July 5, 2023, 10:31am UTC](https://forum.inductiveautomation.com/t/ignition-on-mac-installer-cant-be-opened-because-apple-cant-check-it/71976/16 "2023-07-05T10:31:28Z")

</div>

Looks like no one is answering this properly, so here goes.

1. Right click on the dmg installer and then choose "Open". You should be able to bypass Apple's checks.
2. Launch "Ignition Design Launcher" and add your local designer. Upon opening you will get an "Launch Error Occured, Downloading of launchclient.jar failed" error. Exit from Ignition Design Launcher
3. Open a terminal and type "sudo su". Then "chown -R username /Users/username/.ignition" where username is your Mac username
4. Relaunch "Ignition Design Launcher"

---

<div class="post-metadata">

**Author:** ![karl1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/karl1/32/51171_2.png) [@karl1](https://forum.inductiveautomation.com/u/karl1)\
**Post date:** [July 5, 2023, 11:45am UTC](https://forum.inductiveautomation.com/t/ignition-on-mac-installer-cant-be-opened-because-apple-cant-check-it/71976/17 "2023-07-05T11:45:46Z")

</div>

Thanks so much for this. I’ll give it a try.

---

<div class="post-metadata">

**Author:** ![jcoffman](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jcoffman/32/6429_2.png) [@jcoffman](https://forum.inductiveautomation.com/u/jcoffman)\
**Post date:** [July 6, 2023, 3:33pm UTC](https://forum.inductiveautomation.com/t/ignition-on-mac-installer-cant-be-opened-because-apple-cant-check-it/71976/18 "2023-07-06T15:33:10Z")

</div>

I just merged in the work to notarize the Ignition Installer and it should be available in the nightly and the next release (8.1.31).

But ill throw my two cents in here for some context:

Notarization of a product as complex as Ignition is not trivial. Signing Mach-O execs from the deepest part of Ignition outwards **while** maintaining hashes/signatures where Ignition requires it in a sane way during a build which happens _many times a day_ without interrupting active development is not something which can be completed without great care. It's obviously not impossible (since its complete now) but as Kevin mentioned had lower priority to other issues which affect a much broader collection of users. In an ideal world we would have the bandwidth to fix all bugs and add new features immediately, but unfortunately that isn't the case, especially when there is (an admittedly grotesque) workaround available for this issue. Especially since most mac users are mainly in it for the Designer and the Designer Launcher has been notarized for some time.

Hope that helps contextualize the delay in this, and I hope merging this improves your Ignition workflow 🙂

Thanks,  
JJ Coffman

EDIT: Updated from 8.1.30 to 8.1.31 to account for the hotfix release

---

<div class="post-metadata">

**Author:** ![karl1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/karl1/32/51171_2.png) [@karl1](https://forum.inductiveautomation.com/u/karl1)\
**Post date:** [July 6, 2023, 5:36pm UTC](https://forum.inductiveautomation.com/t/ignition-on-mac-installer-cant-be-opened-because-apple-cant-check-it/71976/19 "2023-07-06T17:36:51Z")

</div>

Thanks so much for the reply, JJ. Suspected there were complications in getting this done, but have no idea of what’s actually involved. Appreciate you taking the time to reply to this thread.

---

<div class="post-metadata">

**Author:** ![karl1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/karl1/32/51171_2.png) [@karl1](https://forum.inductiveautomation.com/u/karl1)\
**Post date:** [July 12, 2023, 7:17pm UTC](https://forum.inductiveautomation.com/t/ignition-on-mac-installer-cant-be-opened-because-apple-cant-check-it/71976/20 "2023-07-12T19:17:17Z")

</div>

To expand on this (for anyone who is interested in trying):

1. Right click on the dmg image
2. Choose open
3. When you get the warning messages, you should have an "Open" button (which I read as "open anyways").  
This will happen 2-3 times during the installation process.

This then seems to tak you through the normal installation process.
