8

I encountered the same issue today with a suggestion: Prepending bundle exec to your command may solve this.

Prepending bundle exec didn't help (I was doing that already).

spring stop & spring restart did not help.

I need to do : bundle update spring that works for me.

is there any better solution to fix using the spring version in previous gemlock file?

techdreams
  • 5,371
  • 7
  • 42
  • 63
Jaswinder
  • 1,455
  • 14
  • 27

3 Answers3

9

I delete gemfile.lock and run bundle that usually clears things up.

Otherwise just remove gem "spring" from Gemfile and run bundle

thedanotto
  • 6,895
  • 5
  • 45
  • 43
3

In my case I fixed this issue by running this command

bundle update spring
techdreams
  • 5,371
  • 7
  • 42
  • 63
0

In my case I was not using the newer spring version anywhere, so running gem uninstall spring and selecting the option to delete the 1.3.6 version solved my problem. This way I did not have to change the Gemfile.lock file.

Mono
  • 302
  • 2
  • 6
  • 21