# Julia won't open after updating MacOS "julia” can’t be opened because Julia is not allowed.."

**URL:** <https://discourse.julialang.org/t/julia-wont-open-after-updating-macos-julia-can-t-be-opened-because-julia-is-not-allowed/126199>\
**Category:** General Usage\
**Tags:** question\
**Created:** [February 22, 2025, 10:20pm UTC](https://discourse.julialang.org/t/julia-wont-open-after-updating-macos-julia-can-t-be-opened-because-julia-is-not-allowed/126199 "2025-02-22T22:20:42Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![PeX](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pex/32/49986_2.png) [@PeX](https://discourse.julialang.org/u/PeX)\
**Post date:** [February 22, 2025, 10:20pm UTC](https://discourse.julialang.org/t/julia-wont-open-after-updating-macos-julia-can-t-be-opened-because-julia-is-not-allowed/126199/1 "2025-02-22T22:20:42Z")

</div>

Hi all,  
I’m using MacBook and after the last update (Sequoia 15.3.1) when I try to open Julia I get the error:  
" **“julia” can’t be opened because Julia is not allowed to open documents in Terminal.**"

I believe this is related to security permissions, but I haven’t been able to find a solution.  
Has anyone else encountered this issue and managed to resolve it?

Thank you!

---

<div class="post-metadata">

**Author:** ![ufechner7](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ufechner7/32/51363_2.png) [@ufechner7](https://discourse.julialang.org/u/ufechner7)\
**Post date:** [February 22, 2025, 11:00pm UTC](https://discourse.julialang.org/t/julia-wont-open-after-updating-macos-julia-can-t-be-opened-because-julia-is-not-allowed/126199/2 "2025-02-22T23:00:42Z")

</div>

How did you install Julia?

If you use `juliaup` there is a good chance to get a signed version of Julia that is accepted by your OS.

---

<div class="post-metadata">

**Author:** ![PeX](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pex/32/49986_2.png) [@PeX](https://discourse.julialang.org/u/PeX)\
**Post date:** [February 23, 2025, 12:17am UTC](https://discourse.julialang.org/t/julia-wont-open-after-updating-macos-julia-can-t-be-opened-because-julia-is-not-allowed/126199/3 "2025-02-23T00:17:54Z")

</div>

I downloaded the .dmg file for MacOS from here:  
[https://julialang.org/downloads/](https://julialang.org/downloads/)

Can you please explain more what do you mean by `juliaup`?

---

<div class="post-metadata">

**Author:** ![ufechner7](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ufechner7/32/51363_2.png) [@ufechner7](https://discourse.julialang.org/u/ufechner7)\
**Post date:** [February 23, 2025, 12:24am UTC](https://discourse.julialang.org/t/julia-wont-open-after-updating-macos-julia-can-t-be-opened-because-julia-is-not-allowed/126199/4 "2025-02-23T00:24:07Z")

</div>

> **[GitHub - JuliaLang/juliaup: Julia installer and version multiplexer](https://github.com/JuliaLang/juliaup?tab=readme-ov-file#mac-linux-and-freebsd)**
>
> Julia installer and version multiplexer

But a `.dmg` file from the link you shared should also be fine. `juliaup` makes it easier to quickly switch Julia versions, so it would be easier to check if a different version perhaps does not have this problem.

---

<div class="post-metadata">

**Author:** ![jballanc](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jballanc/32/328_2.png) [@jballanc](https://discourse.julialang.org/u/jballanc)\
**Post date:** [February 23, 2025, 12:45am UTC](https://discourse.julialang.org/t/julia-wont-open-after-updating-macos-julia-can-t-be-opened-because-julia-is-not-allowed/126199/5 "2025-02-23T00:45:08Z")

</div>

Not sure if this tip will help in this particular circumstance, but…

When you get an error message from macOS related to security permissions, if you immediately open “System Settings…”, go to the “Privacy & Security” preference pane, and scroll down to the section that says “Security”, there will often be a message there mirroring the error you just got with a button you can click to grant the needed permissions.

---

<div class="post-metadata">

**Author:** ![Eben60](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/eben60/32/13475_2.png) [@Eben60](https://discourse.julialang.org/u/Eben60)\
**Post date:** [February 23, 2025, 10:22am UTC](https://discourse.julialang.org/t/julia-wont-open-after-updating-macos-julia-can-t-be-opened-because-julia-is-not-allowed/126199/6 "2025-02-23T10:22:55Z")

</div>

I have macOS 15.3.1, and have no problems with Julia and security permissions.

Generally, the preferred way to install Julia is juliaup.

I’d advise **to remove** Julia you have installed, and install it anew via juliaup. Most probably, it’d solve your problem.

---

<div class="post-metadata">

**Author:** ![giordano](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/giordano/32/2166_2.png) [@giordano](https://discourse.julialang.org/u/giordano)\
**Post date:** [March 10, 2025, 8:21am UTC](https://discourse.julialang.org/t/julia-wont-open-after-updating-macos-julia-can-t-be-opened-because-julia-is-not-allowed/126199/10 "2025-03-10T08:21:06Z")

</div>

Running installation as sudo sounds like a bad idea.

---

<div class="post-metadata">

**Author:** ![tamasgal](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamasgal/32/27946_2.png) [@tamasgal](https://discourse.julialang.org/u/tamasgal)\
**Post date:** [March 10, 2025, 9:10am UTC](https://discourse.julialang.org/t/julia-wont-open-after-updating-macos-julia-can-t-be-opened-because-julia-is-not-allowed/126199/11 "2025-03-10T09:10:55Z")

</div>

Yes absolutely. It would be really good @suski if you’d edit your post since people will pick this up and encounter other errors in future related to “sudo installing” into the home folder. Also, never ever do `sudo` execution of any script on the internet, ever.

To sum up, there are two main ways of installing Julia on macOS:

- Using `juliaup`, **which is the recommended wa** y and it’s the also the very first method at the top of the [Download Julia](https://julialang.org/downloads/) page. It only requires to execute `curl -fsSL https://install.julialang.org | sh` in the terminal, no `sudo`!
- Manually installing using the DMG image file, which might need you to go to the System Settings and grant additional access to the executable, as pointed above by @jballanc In my opinion, this method should be discouraged, unless people know what they are doing.

---

<div class="post-metadata">

**Author:** ![nurban](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nurban/32/5278_2.png) [@nurban](https://discourse.julialang.org/u/nurban)\
**Post date:** [March 23, 2025, 6:19pm UTC](https://discourse.julialang.org/t/julia-wont-open-after-updating-macos-julia-can-t-be-opened-because-julia-is-not-allowed/126199/12 "2025-03-23T18:19:51Z")

</div>

This still doesn’t work for me when I install from DMG - the system settings doesn’t show me an error message or a place where I can grant permissions to the application. `juliaup` doesn’t install the Julia.app Mac application itself into the /Applications folder as the DMG installer does, it just manages a local copy of the `julia` binary. The Mac app used to work and would launch the binary in a new Terminal window. What is the recommended way to get the Julia.app application itself to install and run from the Finder?

---

<div class="post-metadata">

**Author:** ![Eben60](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/eben60/32/13475_2.png) [@Eben60](https://discourse.julialang.org/u/Eben60)\
**Post date:** [March 23, 2025, 9:56pm UTC](https://discourse.julialang.org/t/julia-wont-open-after-updating-macos-julia-can-t-be-opened-because-julia-is-not-allowed/126199/13 "2025-03-23T21:56:53Z")

</div>

> [@nurban](#):
>
> What is the recommended way to get the Julia.app application itself to install and run from the Finder?

What is the use case? Having a double-clickable icon? - Then maybe install Julia by juliaup, and create a shell script for starting Julia.

---

<div class="post-metadata">

**Author:** ![ufechner7](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ufechner7/32/51363_2.png) [@ufechner7](https://discourse.julialang.org/u/ufechner7)\
**Post date:** [March 23, 2025, 9:58pm UTC](https://discourse.julialang.org/t/julia-wont-open-after-updating-macos-julia-can-t-be-opened-because-julia-is-not-allowed/126199/14 "2025-03-23T21:58:52Z")

</div>

I mean, if the .dmg file doesn’t work it should be removed from the Downloads page…

---

<div class="post-metadata">

**Author:** ![tamasgal](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamasgal/32/27946_2.png) [@tamasgal](https://discourse.julialang.org/u/tamasgal)\
**Post date:** [March 23, 2025, 10:12pm UTC](https://discourse.julialang.org/t/julia-wont-open-after-updating-macos-julia-can-t-be-opened-because-julia-is-not-allowed/126199/15 "2025-03-23T22:12:20Z")

</div>

There are some misconceptions (probably related to bad documentation) about what you get when you install Julia. If you ask me, the DMG method is a total failure, it simply should not exist. People who want to develop code, need to be forced to use the terminal, at least to an extent, so that they understand what’s happening.

Installing Julia is totally easy and just like every other (terminal) application, it usually comes with (at least) one binary, which has to live in a folder that is listed in your `PATH` environment variable, since that is one of the places where your shell searches for when you type in something and press enter, like `julia<enter>`. Every serious developer has at least one terminal window open at all time: there is no need to create double-clickable-icons “to launch a language”. I think this is the root of all evil when it comes to newcomers. I could sing a song about Python IDLE…

The `juliaup` installer does everything for you. It downloads Julia in `~/.julia` and modifies the shell configuration file so that future(!) shell processes (i.e. whenever you open a new terminal tab/window in future), the `julia` command is in your `PATH` and you will enter the Julia REPL when you run that command.

**There is really not more magic going on and nobody should do anything else to install Julia on any system. This is just it, a single command in the terminal.**

The DMG installation method is just a pain in the youknowhere and unfortunately it’s also the preferred method for people who are not comfortable with the terminal/shell, so it’s basically a double shot in both feet and knees. If I had something to say, I’d definitely remove the DMG distribution from the downloads page 😉

---

<div class="post-metadata">

**Author:** ![StevenSiew](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stevensiew/32/218393_2.png) [@StevenSiew](https://discourse.julialang.org/u/StevenSiew)\
**Post date:** [March 24, 2025, 12:56am UTC](https://discourse.julialang.org/t/julia-wont-open-after-updating-macos-julia-can-t-be-opened-because-julia-is-not-allowed/126199/16 "2025-03-24T00:56:54Z")

</div>

This is because for MAC, the instructions for DMG says the step below is OPTIONAL when it is for 99% of the people not optional:

### [Optional: Add Julia to PATH](https://julialang.org/downloads/platform/#optional_add_julia_to_path)

If you want to launch Julia from the command line, first [open a new terminal window](https://www.howtogeek.com/682770/how-to-open-the-terminal-on-a-mac/), then run the following snippet from your [shell](https://superuser.com/questions/144666/what-is-the-difference-between-shell-console-and-terminal) (e.g., using the Terminal app, not inside the Julia prompt).

```julia-auto
sudo mkdir -p /usr/local/bin
sudo rm -f /usr/local/bin/julia
sudo ln -s /Applications/Julia-1.11.app/Contents/Resources/julia/bin/julia /usr/local/bin/julia

```

This code creates a [symlink](https://en.wikipedia.org/wiki/Symbolic_link) to a Julia version (here 1.11) of your choosing. To launch Julia, simply type `julia` inside your shell and press return.

---

<div class="post-metadata">

**Author:** ![StevenSiew](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stevensiew/32/218393_2.png) [@StevenSiew](https://discourse.julialang.org/u/StevenSiew)\
**Post date:** [March 24, 2025, 1:08am UTC](https://discourse.julialang.org/t/julia-wont-open-after-updating-macos-julia-can-t-be-opened-because-julia-is-not-allowed/126199/17 "2025-03-24T01:08:03Z")

</div>

When you say something is optional then for all newcomers and newbies, they WILL assume that it is optional and NOT something they HAD TO DO.

When writing instructions, you need to think like a newbie and not like a C guru or Unix guru.

---

<div class="post-metadata">

**Author:** ![Eben60](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/eben60/32/13475_2.png) [@Eben60](https://discourse.julialang.org/u/Eben60)\
**Post date:** [March 24, 2025, 4:12pm UTC](https://discourse.julialang.org/t/julia-wont-open-after-updating-macos-julia-can-t-be-opened-because-julia-is-not-allowed/126199/18 "2025-03-24T16:12:04Z")

</div>

The instructions are pretty clear: “Use `juliaup`”

Those who chose different pathway after such a clear recommendation are either experts knowing what they are doing (for those adding to PATH is optional), or newbies looking for trouble and gathering experience the hard way. Well, their own choice. Learning a bit about how unixes work could be quite useful anyway.

---

<div class="post-metadata">

**Author:** ![Eben60](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/eben60/32/13475_2.png) [@Eben60](https://discourse.julialang.org/u/Eben60)\
**Post date:** [March 24, 2025, 6:02pm UTC](https://discourse.julialang.org/t/julia-wont-open-after-updating-macos-julia-can-t-be-opened-because-julia-is-not-allowed/126199/19 "2025-03-24T18:02:59Z")

</div>

> [@ufechner7](#):
>
> I mean, if the .dmg file doesn’t work it should be removed from the Downloads page…

It worked, and presumably still works. Just you have to add Julia manually to PATH, maybe set up path in the VScode, and, for newer macOS versions, deal with security permissions, for which you might need an admin account. There might be some use cases for DMG installer however.

---

<div class="post-metadata">

**Author:** ![nurban](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nurban/32/5278_2.png) [@nurban](https://discourse.julialang.org/u/nurban)\
**Post date:** [March 30, 2025, 7:44pm UTC](https://discourse.julialang.org/t/julia-wont-open-after-updating-macos-julia-can-t-be-opened-because-julia-is-not-allowed/126199/20 "2025-03-30T19:44:58Z")

</div>

Yes, that’s the use case. I already know how to install Julia (with or without the DMG) and run it from the Terminal. The current DMG installer does not work: it installs an app, but that app cannot be launched from the Finder. This used to work (it launched the Terminal and Julia from there.) If Julia doesn’t want to support Julia.app as a GUI application or wants you to write your own, fine, but then they shouldn’t have the DMG install one in the first place - this is just a broken user experience on the Mac.

---

<div class="post-metadata">

**Author:** ![Eben60](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/eben60/32/13475_2.png) [@Eben60](https://discourse.julialang.org/u/Eben60)\
**Post date:** [March 30, 2025, 7:49pm UTC](https://discourse.julialang.org/t/julia-wont-open-after-updating-macos-julia-can-t-be-opened-because-julia-is-not-allowed/126199/21 "2025-03-30T19:49:59Z")

</div>

> [@nurban](#):
>
> If Julia doesn’t want to support Julia.app as a GUI application

I have completely switched to `juliaup` installation a while ago, but as far as I remember, a double-click onto Julia app installed through DMG just opened the terminal window with a Julia process. Which GUI do you mean?

---

<div class="post-metadata">

**Author:** ![nurban](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nurban/32/5278_2.png) [@nurban](https://discourse.julialang.org/u/nurban)\
**Post date:** [March 30, 2025, 8:13pm UTC](https://discourse.julialang.org/t/julia-wont-open-after-updating-macos-julia-can-t-be-opened-because-julia-is-not-allowed/126199/22 "2025-03-30T20:13:59Z")

</div>

Double-clicking on the app installed from the DMG used to open Julia in a new Terminal window from the Finder (GUI), but now gives the error I described earlier.

---

<div class="post-metadata">

**Author:** ![Eben60](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/eben60/32/13475_2.png) [@Eben60](https://discourse.julialang.org/u/Eben60)\
**Post date:** [March 30, 2025, 9:23pm UTC](https://discourse.julialang.org/t/julia-wont-open-after-updating-macos-julia-can-t-be-opened-because-julia-is-not-allowed/126199/23 "2025-03-30T21:23:07Z")

</div>

OK, I’ve downloaded a DMG, installed Julia, and indeed got the message from the system:

> “julia” can’t be opened because Julia is not allowed to open documents in Terminal.

or

> “julia” can’t be opened because Julia is not allowed to open documents in Terminal.

(got a different message on the second attempt).

BTW for a person looking for help, providing details like the exact message from OS improves the chances 😉

The issue is probably due to a [known bug by Apple](https://developer.apple.com/forums/thread/723842). There might be some workarounds, but I don’t see it being worth the trouble, `juliaup` being available. The bug exists only in relatively new versions of macOS, thus the DMG approach is probably usable on older installations.

> [@nurban](#):
>
> If Julia doesn’t want to support Julia.app

@nurban surely you know **Julia** is not a person 😄

On a more serious note, `Julia` development and distribution is a free service to the community done without a backing by a Google, Microsoft, or like. There is no evil will, just chronically limited resources.

Still, in this case, at least a warning should be provided on the download page.

[Next page](https://discourse.julialang.org/t/julia-wont-open-after-updating-macos-julia-can-t-be-opened-because-julia-is-not-allowed/126199.md?page=2)