# Julia 1.2 not signed correctly on macOS?

**URL:** <https://discourse.julialang.org/t/julia-1-2-not-signed-correctly-on-macos/28396>\
**Category:** New to Julia\
**Created:** [September 5, 2019, 2:14am UTC](https://discourse.julialang.org/t/julia-1-2-not-signed-correctly-on-macos/28396 "2019-09-05T02:14:30Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![dgleich](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dgleich/32/1494_2.png) [@dgleich](https://discourse.julialang.org/u/dgleich)\
**Post date:** [September 5, 2019, 2:14am UTC](https://discourse.julialang.org/t/julia-1-2-not-signed-correctly-on-macos/28396/1 "2019-09-05T02:14:30Z")

</div>

I’m not new to Julia, but when I downloaded the macOS package for Julia, opened it, moved the package to the Applications directory, and launched it, I get.

**“Julia-1.2” can’t be opened because it is from an unidentified developer.**

Your security preferences allow installation of only apps from the App Store and identified developers.

Chrome downloaded this file today at 10:11 PM from **[julialang.org](http://julialang.org)**.

Now, I know how to override this, but I seem to remember all the previous versions of Julia working without any overrides.

Have I simply forgotten (possible…) or did something change with signing the macOS build? I also searched and searched for ‘unidentified developer’ ‘julia’

I’m on Mojave 10.14.6

---

<div class="post-metadata">

**Author:** ![greg\_plowman](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/greg_plowman/32/8100_2.png) [@greg\_plowman](https://discourse.julialang.org/u/greg_plowman)\
**Post date:** [September 5, 2019, 2:50am UTC](https://discourse.julialang.org/t/julia-1-2-not-signed-correctly-on-macos/28396/2 "2019-09-05T02:50:13Z")

</div>

Xref: [https://github.com/JuliaLang/julia/issues/33141](https://github.com/JuliaLang/julia/issues/33141)

---

<div class="post-metadata">

**Author:** ![dgleich](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dgleich/32/1494_2.png) [@dgleich](https://discourse.julialang.org/u/dgleich)\
**Post date:** [September 5, 2019, 1:21pm UTC](https://discourse.julialang.org/t/julia-1-2-not-signed-correctly-on-macos/28396/3 "2019-09-05T13:21:56Z")

</div>

Thanks – I figured someone must have reported this but I really couldn’t find it!

---

<div class="post-metadata">

**Author:** ![filipebraida](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/filipebraida/32/861_2.png) [@filipebraida](https://discourse.julialang.org/u/filipebraida)\
**Post date:** [October 8, 2019, 2:39pm UTC](https://discourse.julialang.org/t/julia-1-2-not-signed-correctly-on-macos/28396/4 "2019-10-08T14:39:50Z")

</div>

It is happening again in the new version of MacOS.

---

<div class="post-metadata">

**Author:** ![mbauman](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mbauman/32/31082_2.png) [@mbauman](https://discourse.julialang.org/u/mbauman)\
**Post date:** [October 8, 2019, 2:57pm UTC](https://discourse.julialang.org/t/julia-1-2-not-signed-correctly-on-macos/28396/5 "2019-10-08T14:57:29Z")

</div>

This is a new issue. MacOS Catalina is now asking for “Notarization” in addition to code signing. It’s on our radar and hopefully we’ll find a workable solution soon. In the meantime, you can right-click on the app and “open” it manually (I think; haven’t updated myself yet).

[https://github.com/JuliaLang/julia/issues/33331](https://github.com/JuliaLang/julia/issues/33331)