No version set for ...

[asdf-vm]

No version set for ...

[henrik]

I got the error

asdf: No version set for command bundle

trying to run bundle after upgrading Ruby via asdf. The error message was confusing, suggesting versions earlier than the one I had installed (2.5.5):

$ bundle
asdf: No version set for command bundle
you might want to add one of the following in your .tool-versions file:

ruby 1.9.3-p551
ruby 2.2.5
ruby 2.4.1
ruby 2.4.4
ruby 2.5.1

What fixed it for me was simply to gem install bundle.

[HashNuke]

@maarek can you get me the following info?

• path where you have the .tool-versions file
• contents of the .tool-versions file
• command you tried to run
• any errors you get

Incase you don't have a .tool-versions file, that's how you set versions (globally or in the project directory). Here's some info about it https://github.com/HashNuke/asdf#the-tool-versions-file

[bxt]

For me the problem was that the .ruby-version file in my current directory had a version I did not install before.

[gaelant]

I got the error

asdf: No version set for command bundle

trying to run bundle after upgrading Ruby via asdf. The error message was confusing, suggesting versions earlier than the one I had installed (2.5.5):

$ bundle
asdf: No version set for command bundle
you might want to add one of the following in your .tool-versions file:

ruby 1.9.3-p551
ruby 2.2.5
ruby 2.4.1
ruby 2.4.4
ruby 2.5.1

What fixed it for me was simply to gem install bundle.

Also for people who recently upgraded Ruby, don't forget to run bundle install after @henrik 's suggestion.

[HashNuke]

@maarek Checked with zsh and pushed a fix.

• Please run git pull origin master within your $HOME/.asdf dir

• In your .zshrc, change the following:

  source $HOME/asdf/.asdf.sh
  to
  . $HOME/asdf/.asdf.sh

I changed the installation instructions too. In short, use the dot operator instead of source. Let me know how it goes.

[maarek]

@HashNuke I modified to you instructions and it's still not finding a version set for the install. I tried wiping the .asdf directory and starting over as well without any luck.

[maarek]

@HashNuke That was it. Didn't realize it was something that needed to be done (at least globally).