I'm getting the folowing error after login:
Invariant Violation: Minified React error #31; visit https://reactjs.org/docs/error-decoder.html?invariant=31&args[]=TypeError%3A%20Cannot%20read%20property%20'expires_at'%20of%20undefined&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
This is hapening on netlify-cms: 2.6.1
@waigs what was causing the error and what solved it?
Having the exact same problem
Having the same issue...
me too...
actually a different issue; i'll open a new one...
Reopening
Please share your configuration so we can get to the bottom of this
@waigs would love to get your input on the subject
Just to give more details.
this is only happening in development, on a local server. the /admin login page tries to call /.netlify/identity/token. this fails probably because there is no such a route locally. While on netlify, it's provided by netlify itself.
My current theory is that perhaps /admin is not supposed to be used in a local development environment. But then, this is not mentioned anywhere (at least I haven't seen it).
@obedm503 if you clear your cache and enter the url of your live environment on Netlify (https://yoursite.netlify.com/), does that fix the error @obedm503?
@tomrutgers it works perfectly fine in the live environment. it only breaks when running a local server.
I'm using the gatsby template and running gatsby serve command
@obedm503 what version of netlify-cms is getting served up? can you look in the inspector console and report
I am having this issue on my live site once I transferred to my own domain.
@obedm503 Sorry for the confusion but I was talking about localhost. If you visit your admin login on localhost, git gateway asks where it can find the live site to make connection to the Netlify Identity settings. If you clear your cache, you get asked for this url again.
@talves not sure what you mean by the "inspector console", but I have version 2.8.0 in my node_modules
Ok, so 2.8.0 has an error for sure. Can you do a yarn add netlify-cms@beta from the terminal and test it out to see if it fixes it. The 2.8.0 has a breaking change for the gatsby plugin.
Although this may not be the core issue, you want to be using the beta release to test against until we get the next release out.
tried it, and it works!
I tried login in and editing a page, but it edited the files on github instead of the local pages. perhaps that's for a different issue
@obedm503 Ok. Glad it works now.
You realize it will not write changes to your local file system. See https://github.com/netlify/netlify-cms/issues/329
I have a beta file-system backend that works with Gatsby, but it's waiting on some changes to the plugin before I release it for general use.
@paulkn can you try the beta release also. I am going to close this for now.
[email protected] has been released. You should all see these fixed once you bump to the latest version. Please open a new issue for any errors.
Most helpful comment
@waigs what was causing the error and what solved it?