next.js + expo: You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports

Question

When I try to run yarn ios, I get:

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 `MyApp`.

But my App.tsx, has:


class MyApp extends App {


  render() {
    const { Component, pageProps } = this.props;
    return (
      <ThemeProvider theme={theme}>
        <ScrollView>
          <Component {...pageProps} />
        </ScrollView>
        <FooterBar />
      </ThemeProvider>
    )
  }
}

export default MyApp

So I'm not sure what it's complaining about?

[This](https://stackoverflow.com/questions/42813342/react-createelement-type-is-invalid-expected-a-string) might help you. The `Component` might be exported incorrectly. — Sunil Chaudhary, May 01 '20 at 16:56
I'm pretty sure its because you need _app.tsx instead of App.tsx? Show me the import statements at the top of your file regardless please — Shanon Jackson, May 08 '20 at 03:36

score 1 · Answer 1 · answered May 08 '20 at 02:45

1

Try importing the component directly from its origin and plugging in your pageProp after. So in example :

import {Component} from '../pathOfComponent';

answered May 08 '20 at 02:45

Uluc Ozdenvar

59
1
7

score 1 · Answer 2 · answered May 08 '20 at 05:27

1

You most likely are not passing anything in this.props.Component. Javascript is quite tricky, if the element does not exist it will treat it as undefined

answered May 08 '20 at 05:27

Prashanth M

326
1
7

I’m using next.js and somehow that’s handling the Component. – Shamoon May 08 '20 at 08:11

next.js + expo: You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports

2 Answers2