Skip to content
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

Can't get Heroku to load this buildpack #7

Closed
jesshmusic opened this issue Dec 2, 2017 · 3 comments
Closed

Can't get Heroku to load this buildpack #7

jesshmusic opened this issue Dec 2, 2017 · 3 comments

Comments

@jesshmusic
Copy link

I am trying to deploy a React app using the create-react-app-buildpack that needs to load puppeteer dependencies for react-snap.
When deploying I am getting this error, which actually seems to freeze the build process on Heroku:

(node:629) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: Failed to launch chrome!
/tmp/build_2e66391b352738bb3c9a1b44c5632458/jesshmusic-living_music_database-ca09d15273a13f10f1a1a9e7ffd147503a55dc26/node_modules/react-snap/node_modules/puppeteer/.local-chromium/linux-499413/chrome-linux/chrome: error while loading shared libraries: libXss.so.1: cannot open shared object file: No such file or directory
TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md
(node:629) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

I have attempted to add the puppeteer build pack as described in the troubleshooting link above but it doesn't do any good.
As a matter of fact Heroku does not load the buildpack at all.
My Heroku build packs are listed as:

1. https://github.com/mars/create-react-app-buildpack.git
2. https://github.com/jontewks/puppeteer-heroku-buildpack.git
@jontewks
Copy link
Owner

jontewks commented Dec 6, 2017

@jesshmusic can you try it with the puppeteer buildpack first in the list? I remember someone mentioning that order mattered when installing dependencies. Other than that I don't think I'll be able to help out, since this issue is getting another buildpack to run correctly and not just puppeteer.

@jontewks jontewks closed this as completed Dec 6, 2017
@jamesmosier
Copy link

jamesmosier commented Jan 8, 2018

For what it's worth, order helped fix this error for me. I had to put the puppeteer buildpack before the Node buildpack and then it worked!
screen shot 2018-01-07 at 9 43 21 pm

@jontewks
Copy link
Owner

jontewks commented Jan 9, 2018

Thanks for the info. Interesting that on our production use of it we have my buildpack second:
image
I'll definitely keep it in mind about potential troubleshooting solutions though if people are experiencing weird issues in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants