Error after upgrade from next.js 15.2 to 16
Unanswered
Spectacled bear posted this in #help-forum
Spectacled bearOP
Hello guys, i upgraded the version of next.js to the latest 16.0.0 and i try to run my application, the landing page is okay, after i click any route i got this error:
An unknown Component is an async Client Component. Only Server Components can be async at the moment. This error is often caused by accidentally adding
Even though the application was working very good with 15.2 version. There is no client component as async
An unknown Component is an async Client Component. Only Server Components can be async at the moment. This error is often caused by accidentally adding
'use client' to a module that was originally written for the server.Even though the application was working very good with 15.2 version. There is no client component as async
17 Replies
@Spectacled bear Hello guys, i upgraded the version of next.js to the latest 16.0.0 and i try to run my application, the landing page is okay, after i click any route i got this error:
An unknown Component is an async Client Component. Only Server Components can be async at the moment. This error is often caused by accidentally adding `'use client'` to a module that was originally written for the server.
Even though the application was working very good with 15.2 version. There is no client component as async
i dont have issue with this when migrating to 16. is it okay if we investigate what component is causing this issue?
@alfonsüs ardani i dont have issue with this when migrating to 16. is it okay if we investigate what component is causing this issue?
Spectacled bearOP
Yes but meanwhile i found that only if i navigate through the application the route with <Link> im having this issue. When i try to search in my browser directly the route it works fine
@Spectacled bear Yes but meanwhile i found that only if i navigate through the application the route with <Link> im having this issue. When i try to search in my browser directly the route it works fine
yes can we know the name of the component and where it is located?
Spectacled bearOP
Which component exactly?
@Spectacled bear Which component exactly?
what does the error looks like?
Spectacled bearOP
@Spectacled bear Click to see attachment
can we see whats at inpage.js?
Spectacled bearOP
Spectacled bearOP
the error on incognito browser:
@Spectacled bear We're hitting the same thing, introduced going from 16-beta.0 to 16
Spectacled bearOP
@Matt u found out any way to solve it?
We just revered back to beta and it’s been fine
@Spectacled bear Click to see attachment
Spectacled bear
At first glance, it looks like it could be a browser extension causing it? Do you have browser extensions disabled in incognito?
In our case it can't be a browser extension. We package our app in a WKWebView in an iOS app bundle that doesnt' support extensions
Not sure for other cases
@Spectacled bear At first glance, it looks like it could be a browser extension causing it? Do you have browser extensions disabled in incognito?
Spectacled bearOP
Yes, I tried with incognito browser where no extension was installed and the same problem appeared