-
Notifications
You must be signed in to change notification settings - Fork 153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No longer works on the heroku-16 stack #2
Comments
What if I split this repo into another one supporting Heroku-16 with a commit before merging #1 ? |
I solved it for me by upgrading to heroku-18, so not for my sake. :) |
This was not solved by upgrading to heroku-18 for us. The contents of |
any update on this? I'm also getting contents of |
I believe I'm running into the same issue as others here on heroku-18. I'm seeing this in the heroku logs indicating that the file is created in the wrong directory:
|
We ended up resolving this without a buildpack. We stored our raw credentials JSON in a
Code in the |
@heavyperil that worked for me as well, thanks! |
I probably won't update this repo since different solutions seem to work for different people and their respective Heroku stack versions. I encourage forking or finding another solution since the repo itself only contains a few lines of code. |
A few days ago, #1 was merged, and the compile script uses the syntax
${GOOGLE_CREDENTIALS@Q}
which was introduced in bash 4.4.The heroku-16 stack has bash 4.3.48, so this buildpack no longer works there (but on heroku-18 it works fine).
The text was updated successfully, but these errors were encountered: