Cannot read property 'getIn' of undefined
See original GitHub issueI’m getting error when rendering
<OAuthSignInButton
provider=...
endpoint=... />
I’m specifying both required provider
and endpoint
props, but I get this error:
Uncaught TypeError: Cannot read property 'getIn' of undefined
Issue Analytics
- State:
- Created 8 years ago
- Reactions:1
- Comments:34 (6 by maintainers)
Top Results From Across the Web
Cannot read property 'getIn' of undefined · Issue #2332 · ...
It seems that the editor detects the target is a DraftJS based on its markup structure but doesn't check it is its own...
Read more >reactjs - draft-js Cannot read property 'getIn' of undefined ...
I meet the same problem. It looks like because call editorState.getBlockTree(anchorBlockKey).getIn(...) in getUpdatedSelectionState.js the ...
Read more >[Solved]-draft-js Cannot read property 'getIn' of undefined ...
I meet the same problem. It looks like because call editorState.getBlockTree(anchorBlockKey).getIn(...) in getUpdatedSelectionState.js the editorState.
Read more >Draft-Js Cannot Read Property 'Getin' Of Undefined ...
Clicking nested editor having readOnlyfalse throws error getUpdatedSelectionState.js:32 Uncaught TypeError: Cannot read property 'getIn' of undefined. Clicking ...
Read more >How to Avoid Getting 'Cannot read property of undefined' in ...
This error occurs when you try to read or access a property on an object that is undefined . Another common case that...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I got the same error, which seemed to be caused by not having the reducer specified
It’d be nice if it handled this a bit better, either handling the null value, or returning an error telling people what to do. Also, the instructions in the README don’t mention setting up the reducer. The example app certainly has it in there, but it also has a lot of other stuff that a real app doesn’t need.
Hi @lynndylanhurley ,
I just hardcoded every container of redux-auth so it access the auth state like this:
And is working, I believe that if we isolate the selector in a module so it handles the immutable case (like in my previous post) for the meanwhile, then we could further give the users the ability to customize this selector. If you guide me a bit I could help you with a PR.