Open benjamin-hull opened 9 years ago
Same here, but ruby 2.2.0 and cedar.
Have you tried reversing the order of the buildpacks listed in .buildpacks? i had a similar issue, with a Python stack. It seems that the multi-buildpack uses the release configuration from the buildpack listed last.
Reversing the buildpacks worked for me
Reversing the buildpacks didn't seem to work for me. RGeo::Geos.supported?
still returns false
.
@allthesignals Did you get this to work? I've tried reversing buildpacks and purging the repo but to no avail.
@jkogara No luck. I had to create a custom Dockerfile to get it to work.
any luck for someone else without Dockerfiles?
This may be related to other recent issues that have come up. My Rails app on Heroku recently started erroring when any geometry based operation was attempted.
I've updated heroku-geo-buildpack, checked references, switched stack to cedar-14. The deployment and build process seems to work fine, but
RGeo::Geos.supported?
always returnsfalse
.This is under Ruby 2.1.5. My .buildpacks file looks like:
Here's the start of my deploy log (looks fine to me)
I have tried purging the repo cache, rebuilding, and many different forks of this buildpack that try to fix this issue, but it hasn't made any difference.
Are you able to suggest anything else to workaround or diagnose the issue?
Thank you!