#registration flow - nextjs app router

1 messages · Page 1 of 1 (latest)

versed crescent
#

during the registration process I get a "application error: a client-side exception has occured" on windows/android devices but not iOS/macOS devices

TypeError: a.default.defectStore(...) is undefined h1-check.js1:1301
Error: Promised response from onMessage listener went out of scope vendors.chunk.js:1:525956
TypeError: r[e.aaguid] is undefined

terse basinBOT
#

Hi @versed crescent. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

#

Based on the knowledge sources provided, it seems like you're encountering a client-side exception during the registration process in your Next.js application. However, the specific error messages you provided are not directly addressed in the available sources.

One of the issues mentioned in the sources is a client-side exception that occurs when a user has a tab open to a site for a while, and a new version of the site is deployed. When the user navigates back to that tab, an "Application error: a client-side exception has occurred" error is thrown. This error goes away once the user refreshes the page. The issue seems to be related to old site assets no longer existing and throwing 404 errors (source (https://github.com/vercel/next.js/issues/48635)).

However, without more specific information about your application and the context in which the error occurs, it's difficult to provide a definitive solution. It's recommended to check the deployment process and how assets are managed during updates. Also, consider checking the compatibility of your code with different operating systems and browsers, as the error seems to occur only on certain devices.

For handling authentication in Next.js, there are several solutions that support the App Router, such as NextAuth.js, Clerk, Stack Auth, Lucia, Auth0, Stytch, Kinde, WorkOS, or manually handling sessions or JWTs (source (https://nextjs.org/docs/app#how-can-i-handle-authentication-with-the-app-router)).

If the issue persists, consider opening an issue on the Next.js GitHub repository or seeking help from the Next.js community.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: