anthonator
I currently have an umbrella application with 5 child apps. One of the applications defines uuid as a test dependency. Another application defines sentry as a general dependency. sentry defines uuid as a general dependency.
When I compile in dev I get the following error:
Unchecked dependencies for environment dev:
* uuid (Hex package)
the dependency is not locked. To generate the "mix.lock" file run "mix deps.get"
** (Mix) Can't continue due to errors on dependencies
If I remove sentry the issue goes away. If I compile using MIX_ENV=test the issue goes away. If I define uuid as a general dependency the issue goes away.
It seems that me defining uuid as a test dependency and sentry defining uuid as a general dependency is creating some sort of conflict.
Has anybody experienced this before? Does this seem like a bug or intended behavior? It seems concerning to me that an umbrella applications dependencies can be in conflict with the dependencies of a dependency based on it’s environment definition. This isn’t even a version issue. Both sentry and my application define uuid as ~> 1.0.
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
We build reliable cloud platforms for business-critical systems.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixir-ls
- #ai
- #elixirconf-us
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Enabling companies to succeed by building software people love.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
josevalim
What is your Elixir version? How are you defining the test dependency? Elixir was supposed to catch this and ask you to make sure uuid is a available on all environments.
anthonator
I’m using Elixir 1.5.
Here’s how I’m defining it:
Is it expected that I have to define
uuidas a regular dependency (rather than a test dependency) if another dependency requiresuuid?anthonator
I’m seeing the same thing using Elixir 1.5.1
josevalim
You are expected to do it BUT mix was supposed to tell you so instead of letting you figure it out by yourself. Can you please open up a bug report with an app that reproduces the issue?