Jake

Yep, I have the same issue. My third cventry is squished too closely to my second entry. The fix provided by @rikudoukarthik worked for me. What are the consequences for...

I'm getting the same issue but adding that import to /models/index.js didn't solve it for me. I followed the steps listed in the readme, no other changes made, and get...

Nevermind, I totally forgot that .env is ignored by git so I need to recreate it after pulling from my local repo. It's all good, working now.

So I've got most of it sorted, it's just this section that's giving me grief: ``` const getMe = async (req) => { const token = req.headers['x-token'] if (token) {...

I've got it working. I'll close the issue but here's the solution for anyone else trying to do this: 1. Change the getMe function (starts line 24 in /src/index.js) to:...

Actually ignore my last comment. res.set isn't working. It just keeps using the same refresh token in the client to create a new auth token, but it doesn't send the...

I managed to get it working, although I'm using Next.js and cookies to store the data rather than local storage (since you can't access local storage on the server side)....

So the solution was simple. I just changed the server schema so that the return value from the subscription isn't required. E.g. from https://github.com/the-road-to-graphql/fullstack-apollo-express-postgresql-boilerplate/blob/master/src/schema/message.js ``` - line 32: messageCreated: MessageCreated!...

I'm still confused about it. Like I said, the schema runs fine in graphql playground so I shouldn't have had to adjust the server schema - it must be an...

I'm getting this error message too, even though my .pem files are directly copied from the server where they were generated from. Anyone know what the deal is? Is this...