Initial SSR Fails on Deploy about next-with-apollo HOT 12 CLOSED

we finally got everything working. had to do some work with changing the headers because of heroku. thanks for your help!

from next-with-apollo.

i'd be happy to link any other files or code snippets if they'll help also

from next-with-apollo.

Hi @holdeelocks , what's the result of this:

if (ctx.req && ctx.req.headers) {
		console.log(ctx.req.headers, "request headers");
	}

Does it have the headers that you need ?

Btw does it works when you run the project with next build && next start ? it may be related to a external thing changing the headers (like express)

from next-with-apollo.

The headers(cookies) we need aren't showing up in that console.log. We're using a custom server.js file to do routing for our app. Our build commands are start: NODE_ENV=production node server.js and heroku-postbuild: next build. Could it be something to do with the custom express server or the way that we're starting it on heroku?

from next-with-apollo.

Here's a link to our frontend repo if that helps give you some context to what our code is like: https://github.com/up4life/frontend. It's a lot of code but the most relevant parts are in /utils/withData.js /pages/index.js server.js and /pages/_app.js

from next-with-apollo.

@holdeelocks but does it work with a local build ? (the one generated with next build), I may try to run your project later though

from next-with-apollo.

Yeah the cookies are in the request headers if I run next build && next start or next build && node server.js locally. Both commands work as expected.

from next-with-apollo.

@holdeelocks So the app works locally even with a build but fails in Heroku ?

from next-with-apollo.

Yeah exactly

from next-with-apollo.

@holdeelocks it looks like is related to Heroku then, have you tried looking in the docs for the changes they may be doing to the headers ? or anything related, another option is to not pass the headers object directly, but instead just send exactly what you need.

from next-with-apollo.

Yeah I've looked and according to their docs, they shouldn't be messing with our headers since we're using a custom domain. We've looked into other hosting solutions (mostly zeit) but we haven't been able to figure out a way to get our Apollo Server to deploy there.

from next-with-apollo.

Our main point of confusion is where in the process we might be able to intercept the request and keep heroku from removing the cookie header. We've also tried deploying our frontend on Zeit and still run into the same issue, so it's not solely a heroku issue. We have no clue what's causing this..

from next-with-apollo.