josefrichter
Hi. I am trying to update older project to latest elixir, phoenix and all dependencies.
I am still running into (Mix) Could not compile dependency :telemetry
I’ve googled solutions, tried reinstalling rebar, etc. But still can’t figure it out. I have to say I’m a bit out of my depth here.
This is the full error:
❯ mix compile
/bin/sh: -c: line 0: syntax error near unexpected token `('
/bin/sh: -c: line 0: `(/Users/josefrichter/.asdf/installs/elixir/1.14.3-otp-25/.mix/elixir/1-14/rebar3 bare compile --paths /Users/josefrichter/Dropbox (Personal)/code/elixir/organizer/_build/dev/lib/*/ebin'
** (Mix) Could not compile dependency :telemetry, "/Users/josefrichter/.asdf/installs/elixir/1.14.3-otp-25/.mix/elixir/1-14/rebar3 bare compile --paths /Users/josefrichter/Dropbox (Personal)/code/elixir/organizer/_build/dev/lib/*/ebin" command failed. Errors may have been logged above. You can recompile this dependency with "mix deps.compile telemetry", update it with "mix deps.update telemetry" or clean it with "mix deps.clean telemetry"
Any suggestions, please? Thank you.
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Elixir, Erlang & messaging conferences from Code Sync. Next up: ElixirConf US (10–11 Sep) & Code BEAM Europe (21–22 Oct), Haarlem + online.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
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 10- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
D4no0
First of all try to remove the
_builddirectory in your project, then if it doesn’t help make sure that your elixir is compiled with correct OTP version, for example in your case your elixir is compiled with OTP 25, so you should have this version as OTP you are using currently.josefrichter
All this seems to be ok, I tried all that. I even tried to reinstall elixir, rebar, etc. to make sure all versions are correct. But now I’m already running out of ideas.
D4no0
I see you are using the SH, have you tried using bash, I used to have some problems with sh myself, especially on alpine containers.
josefrichter
I’ve been using zsh, but tried toggling to bash and sh too. Still the exact same error.
I am using asdf, if that plays any role.
The clash seems to be between rebar3 and telemetry.
Any ideas, please?
LostKobrakai
I’d suggest trying a path without spaces and/or parenthesis.
BradS2S
Yeah maybe try escaping the white space in the path
LostKobrakai
Usually one is not in control of the places those paths are handled in. Therefore I still suggest avoiding such paths for development to begin with.
josefrichter
That actually worked
Thank you!
BradS2S
I’ve had this exact same issue in the past. It would be nice if the error said something like “destination not found” or something maybe
tristan
Can you open an issue on Elixir about this? It looks like the mix compiler that calls rebar3 isn’t escaping or quoting paths.