TypeError: Cannot set property 'id' of undefined about gatsby-source-google-places HOT 9 CLOSED

Woohoo!

from gatsby-source-google-places.

@hartey11

I just tested with a brand new gatsby default starter and it worked fine with both gatsby develop and gatsby build. I'm not sure what else to tell you other than that it smells like an npm/yarn caching issue where you've still got the old package somehow. It's odd that it happens to you both on Netlify and on locally when you build.

Try running through yarn cache clean and gatsby clean if you haven't already.

I'd like to help you with this I need help reproducing it. Would you create a fresh repo from gatsby new default that reproduces, and link it here (sans API key)? I can pull it and see if I can experience the issue. It really does smell like a caching issue, but linking me to the fresh repo would help rule anything else out.

from gatsby-source-google-places.

@franklintarter yeah I'm at a bit of a loss. Its working fine for me now locally (both develop and build) but I'm still getting the error on netlify, even after deleting my site and starting again.

from gatsby-source-google-places.

@hartey11
Bummer. Maybe something funky happened with your yarn.lock or package.json.lock? You could try deleting those and running yarn or npm install to regenerate them. Then inspect them to make sure they're referencing the 0.0.5 version of this package. Then commit them to see if it helps Netlify pull the right version.

from gatsby-source-google-places.

@franklintarter made some small progress... been able to confirm that netlify is getting the latest version 0.0.5.

So I'm guessing something is stopping the response from being received correctly by netlify. I can see errors are being output to the console from the promise, so maybe google is returning something else or in a different format?

Here's a link to issue I opened on netlify for reference:
https://community.netlify.com/t/updating-node-modules/12087/16

from gatsby-source-google-places.

@hartey11
Interesting. So the old package thing could have been a red herring. I will try my own Netlify deployment a bit later this week and let you know if I can encounter the same issue.

from gatsby-source-google-places.

@hartey11
I stumbled upon what I think could be your issue!

The message you are getting is a red herring. The call to the google API is failing. I would guess the reason is that your API key is not getting set correctly in the Netlify environment. I also forgot to set up my API key and got the same error you've been getting.

I'm going to update the package so that errors from the Google API will get rethrown and the messages can be seen appropriately.

from gatsby-source-google-places.

@hartey11
Okay, I updated the package handle errors from the API so you should see them in the console. Please try yarn add gatsby-source-google-places to update the package to version 0.0.6. Hopefully, you'll see something helpful in your console that will help debug your Netlify issue.

Let me know how that goes.

from gatsby-source-google-places.

@franklintarter you've only gone and sorted it! I was able to debug it straight away with the added handle errors. Turns out there was an issue with my Google Cloud billing account that needed resolving, which I've now fixed and been able to successfully deploy. Not sure why the API key was still working locally though... lol

Thanks for all your help!

from gatsby-source-google-places.