# Fix the “Objects are not valid as a React child” error

> How to fix the Objects are not valid as a React child found object Promise error in the Next.js pages folder by removing async from your page component.

Author: [Flavio Copes](https://flaviocopes.com/about/) | Published: 2023-02-27 | Topics: [React](https://flaviocopes.com/tags/react/) | Canonical: https://flaviocopes.com/fix-the-objects-are-not-valid-as-a-react-child-error/

I had this error in a [React](https://flaviocopes.com/react/) ([Next.js](https://flaviocopes.com/nextjs/)) app:

```
Error: Objects are not valid as a React child (found: [object Promise]).
If you meant to render a collection of children, use an array instead.
```

After some time trying to figure out what the error meant, I figured out I was exporting my page component as async because I copied it from another Next.js project where this is possible because of the use of the app folder:

```js
export default async function Page() {

}
```

But it was not possible in the pages folder.

Removing `async` made it work:

```js
export default function Page() {

}
```