sadmann7 / skateshop

An open source e-commerce skateshop build with everything new in Next.js.
https://skateshop.sadmn.com
MIT License
5.23k stars 745 forks source link

Application error: a server-side exception has occurred (see the server logs for more information). Digest: 2497555049 #77

Closed apex9k closed 1 year ago

apex9k commented 1 year ago

when on the production site and trying and access the dashboard or account a white page with the above error code appears. the console prints out the following error. Signed in with google sso.

8745-c1afa25a7b044c0f.js:1 Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.

joseavr commented 1 year ago

I have the same error. I hope they fix it soon :(

sadmann7 commented 1 year ago

I updated to the latest next version yesterday. This is showing since then maybe.

I will try to fix it today.

apex9k commented 1 year ago

all good this is a cool project and I appreciate the work you have put into it.

sadmann7 commented 1 year ago

thanks a lot, it should be fixed now

joseavr commented 1 year ago

Can you share what was the issue and how u fixed it?


From: Sadman Sakib @.> Sent: Tuesday, October 3, 2023 1:13:14 PM To: sadmann7/skateshop @.> Cc: Valdivia Rojas, Jose A @.>; Comment @.> Subject: Re: [sadmann7/skateshop] Application error: a server-side exception has occurred (see the server logs for more information). Digest: 2497555049 (Issue #77)

thanks a lot, it should be fixed now

— Reply to this email directly, view it on GitHubhttps://github.com/sadmann7/skateshop/issues/77#issuecomment-1745397142, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASWCT7UOJJA64NQI4L6QKTLX5RBSVAVCNFSM6AAAAAA5QAV3GGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBVGM4TOMJUGI. You are receiving this because you commented.Message ID: @.***>

sadmann7 commented 1 year ago

It was most probably because of the clerk or nextjs version, After updating the packages it was working fine.

I am closing the issue

joseavr commented 1 year ago

Thank you mister sadmann