# Is 1.7.2 on Intel Mac missing Codesigning?

**URL:** <https://discourse.julialang.org/t/is-1-7-2-on-intel-mac-missing-codesigning/76099>\
**Category:** General Usage\
**Created:** [February 8, 2022, 11:52am UTC](https://discourse.julialang.org/t/is-1-7-2-on-intel-mac-missing-codesigning/76099 "2022-02-08T11:52:03Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ctkelley](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ctkelley/32/10684_2.png) [@ctkelley](https://discourse.julialang.org/u/ctkelley)\
**Post date:** [February 8, 2022, 11:52am UTC](https://discourse.julialang.org/t/is-1-7-2-on-intel-mac-missing-codesigning/76099/1 "2022-02-08T11:52:03Z")

</div>

Intel Mac, latest OS, got this in a popup

**“julia” can’t be opened because the identity of the developer cannot be confirmed.**

M1 version on Macbook works fine.

---

<div class="post-metadata">

**Author:** ![ctkelley](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ctkelley/32/10684_2.png) [@ctkelley](https://discourse.julialang.org/u/ctkelley)\
**Post date:** [February 8, 2022, 12:09pm UTC](https://discourse.julialang.org/t/is-1-7-2-on-intel-mac-missing-codesigning/76099/2 "2022-02-08T12:09:41Z")

</div>

DId the trick (start with control + click) that worked before. Julia took a long time to start and then I got this

```julia
exec '/Applications/Julia-1.7.app/Contents/Resources/julia/bin/julia'
┌ Warning: The call to compilecache failed to create a usable precompiled cache file for JSON [682c06a0-de6a-54ab-a142-c8b1cf79cde6]
│ exception = Required dependency Parsers [69de0a69-1ddd-5017-9359-2bf0b02dc9f0] failed to load from a cache file.
└ @ Base loading.jl:1132
┌ Warning: Module JSON with build ID 103410392755 is missing from the cache.
│ This may mean JSON [682c06a0-de6a-54ab-a142-c8b1cf79cde6] does not support precompilation but is imported by a module that does.
└ @ Base loading.jl:1107
┌ Warning: The call to compilecache failed to create a usable precompiled cache file for MbedTLS [739be429-bea8-5141-9913-cc70e7f3736d]
│ exception = Required dependency MbedTLS_jll [c8ffd9c3-330d-5841-b78e-0817d7145fa1] failed to load from a cache file.
└ @ Base loading.jl:1132
┌ Warning: The call to compilecache failed to create a usable precompiled cache file for IJulia [7073ff75-c697-5162-941a-fcdaad2a7d2a]
│ exception = Required dependency ZMQ [c2297ded-f4af-51ae-bb23-16f91089e4e1] failed to load from a cache file.
└ @ Base loading.jl:1132
               _
   _ _ _(_)_ | Documentation: https://docs.julialang.org
  (_) | (_) (_) |
   _ _ _| |_ __ _ | Type "?" for help, "]?" for Pkg help.
  | | | | | | |/ _` | |
  | | |_| | | | (_| | | Version 1.7.2 (2022-02-06)
 _/ |\ __'_|_|_|\__'_| | Official https://julialang.org/ release
|__/ |

julia> 

```

When I tried again, seemed to work ok. What did the warnings mean?

And… when I tried a couple hours later on a different Mac (same OS, same Intel) everything worked from the start.

---

<div class="post-metadata">

**Author:** ![Hareruya](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/hareruya/32/47536_2.png) [@Hareruya](https://discourse.julialang.org/u/Hareruya)\
**Post date:** [February 9, 2022, 11:52am UTC](https://discourse.julialang.org/t/is-1-7-2-on-intel-mac-missing-codesigning/76099/4 "2022-02-09T11:52:48Z")

</div>

You can go to System Preferences-\>Security&Privacy, click “open anyway” and enter your password.  
I didn’t have the same issue installing it via homebrew, and it really makes the updating process easier.

---

<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:** [February 9, 2022, 4:08pm UTC](https://discourse.julialang.org/t/is-1-7-2-on-intel-mac-missing-codesigning/76099/5 "2022-02-09T16:08:17Z")

</div>

It sounds like the lack of codesigning may have been a transient issue, as were the compilecache warnings? I believe those warnings just mean that some dependency has a broken `.ji` file — perhaps due to the upgrade — and those will get purged/regenerated automatically as needed.