`Error: Element type is invalid` with react-native-maps v1.0.0
See original GitHub issueAfter updating to v1.0.0 of react-native maps I got the following error:
ERROR Error: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.
Check the render method of `MapViewDirections`.
Issue Analytics
- State:
- Created a year ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Element type is invalid . React Native - Stack Overflow
As you said, this is a common error you can see while developing with React Native. It occurs when the component name is...
Read more >error-element-type-is-invalid-expected-a-string-for-built-in ...
Unable to open 'App.js': Cannot read property 'parentNode' of undefined.
Read more >Element type is invalid: expected a string (for ... - OneCompiler
Getting following error after migrating to material-ui 1.0. Element type is invalid: expected a string (for built-in components) or a class/function (for ...
Read more >Export default class app extends component error - Weebly
Type a JavaScript function to find the difference for two arrays. ... atom javascript es6 linter AttachConsole failed with error 6 : Invalid...
Read more >react-native-router-flux | Yarn - Package Manager
v4.0.0-beta.x is based on React Navigation v1.5.x. ... for Share application #2338; Example project error #2337; Element type is invalid: expected a string....
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
Seems to be a change with the exports of react-native-maps. Here’s a patch that fixes the error for me:
Released as 1.9.0