Why Won't Heroku Accept My Gemfile.Lock in Windows

Why won't Heroku accept my Gemfile.lock in Windows?

Like matt commented above:

The problem is that Bundler creates different Gemfile.locks for Windows. The only solution is to create and commit the lock file on a *NIX system.

I would suggest to create a virtual machine running e.g. Ubuntu – maybe using Virtual Box. You can even get ready-to-use virtual machines – for example here.

Rails - Error pushing to Heroku - not seeing Gemfile.lock

Get rid of all occurrences of -x86-mingw32 in the gem specs as well as lines

PLATFORMS
  x86-mingw32

as Alex mentioned.

I understand why Heroku now requires Gemfile.lock, but overall I disagree with the practice.

Pushing to Heroku fails due to unsupported Ruby version even after Gemfile was changed

Heroku doesn't support Ruby 2.3.1, 2.3.3 or 2.4.0

Look at your log:

remote:  !     An error occurred while installing ruby-2.3.1
remote:  !
remote:  !     This version of Ruby is not available on Heroku-18. The minimum supported version
remote:  !     of Ruby on the Heroku-18 stack can found at:
remote:  !
remote:  !     https://devcenter.heroku.com/articles/ruby-support#supported-runtimes

Look at the link from your log:

Heroku supports the following Ruby versions and the associated Rubygems. A supported version means that you can expect our tools and platform to work with a given version. It also means you can receive technical support. Here are our supported Ruby versions:

MRI:

• 2.4.5 : patchlevel 335, Rubygems: 2.6.14.4
• 2.5.5: patchlevel 157, Rubygems: 2.7.6.2
• 2.6.2: patchlevel 33, Rubygems: 3.0.3

Also read information how to specify Ruby version.

Pay special attention to the Troubleshooting section. Looks like you didn't commit your Gemfile and Gemfile.lock after changing Ruby version and before pushing to Heroku.

---

Related Topics