You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can't post comments due to a client-side exception. When attempting to submit a comment on any post, the action fails with the following error message:
Application error: a client-side exception has occurred (see the browser console for more information).
To Reproduce
Navigate to any post
Enter a comment and submit
Comment fails to post and client-side exception is displayed
Expected behavior
Comments should post successfully without any errors.
Screenshots
Desktop (please complete the following information):
OS: MacOS
Browser Arc, Chromium
Version 1.69.0 (55816), 131.0.6778.70
Additional context
Log
POST https://frontpage.fyi/post/tom.frontpage.team/3lb4xbzioaw2x 500 (Internal Server Error)
(anonymous) @ 525-30b4f38689a333c6.js:14
R @ 525-30b4f38689a333c6.js:1
await in R
j @ 525-30b4f38689a333c6.js:1
d @ 525-30b4f38689a333c6.js:1
action @ 525-30b4f38689a333c6.js:2
l @ 525-30b4f38689a333c6.js:2
(anonymous) @ 525-30b4f38689a333c6.js:2
dispatch @ 525-30b4f38689a333c6.js:2
(anonymous) @ 525-30b4f38689a333c6.js:1
(anonymous) @ 525-30b4f38689a333c6.js:1
t.startTransition @ 525-30b4f38689a333c6.js:2
(anonymous) @ 525-30b4f38689a333c6.js:1
(anonymous) @ 525-30b4f38689a333c6.js:1
s @ 525-30b4f38689a333c6.js:1
n @ 525-30b4f38689a333c6.js:2
l$ @ efe33283-c38f5e3eb7da60e0.js:1
lQ @ efe33283-c38f5e3eb7da60e0.js:1
(anonymous) @ 956-8026582818881808.js:1
t.startTransition @ 525-30b4f38689a333c6.js:2
n @ 956-8026582818881808.js:1
uj @ efe33283-c38f5e3eb7da60e0.js:1
(anonymous) @ efe33283-c38f5e3eb7da60e0.js:1
nC @ efe33283-c38f5e3eb7da60e0.js:1
uq @ efe33283-c38f5e3eb7da60e0.js:1
sY @ efe33283-c38f5e3eb7da60e0.js:1
sq @ efe33283-c38f5e3eb7da60e0.js:1
n @ 525-30b4f38689a333c6.js:14
525-30b4f38689a333c6.js:14 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.
(anonymous) @ 525-30b4f38689a333c6.js:14
window.console.error @ 525-30b4f38689a333c6.js:1
aD @ efe33283-c38f5e3eb7da60e0.js:1
aA @ efe33283-c38f5e3eb7da60e0.js:1
e.callback @ efe33283-c38f5e3eb7da60e0.js:1
oP @ efe33283-c38f5e3eb7da60e0.js:1
oN @ efe33283-c38f5e3eb7da60e0.js:1
oT @ efe33283-c38f5e3eb7da60e0.js:1
oH @ efe33283-c38f5e3eb7da60e0.js:1
o4 @ efe33283-c38f5e3eb7da60e0.js:1
oH @ efe33283-c38f5e3eb7da60e0.js:1
o4 @ efe33283-c38f5e3eb7da60e0.js:1
oH @ efe33283-c38f5e3eb7da60e0.js:1
o4 @ efe33283-c38f5e3eb7da60e0.js:1
oH @ efe33283-c38f5e3eb7da60e0.js:1
o4 @ efe33283-c38f5e3eb7da60e0.js:1
oH @ efe33283-c38f5e3eb7da60e0.js:1
o4 @ efe33283-c38f5e3eb7da60e0.js:1
oH @ efe33283-c38f5e3eb7da60e0.js:1
o4 @ efe33283-c38f5e3eb7da60e0.js:1
oH @ efe33283-c38f5e3eb7da60e0.js:1
o4 @ efe33283-c38f5e3eb7da60e0.js:1
oH @ efe33283-c38f5e3eb7da60e0.js:1
(anonymous) @ efe33283-c38f5e3eb7da60e0.js:1
ud @ efe33283-c38f5e3eb7da60e0.js:1
i8 @ efe33283-c38f5e3eb7da60e0.js:1
i3 @ efe33283-c38f5e3eb7da60e0.js:1
uF @ efe33283-c38f5e3eb7da60e0.js:1
T @ 525-30b4f38689a333c6.js:1
525-30b4f38689a333c6.js:16
POST https://o4508064544391168.ingest.de.sentry.io/api/4508064550551632/envelope/?sentry_key=09bfc307f1fd12228eadd7477e1656c8&sentry_version=7&sentry_client=sentry.javascript.nextjs%2F8.35.0 net::ERR_BLOCKED_BY_CLIENT
(anonymous) @ 525-30b4f38689a333c6.js:16
(anonymous) @ 525-30b4f38689a333c6.js:14
add @ 525-30b4f38689a333c6.js:14
send @ 525-30b4f38689a333c6.js:14
sendEnvelope @ 525-30b4f38689a333c6.js:13
sendSession @ 525-30b4f38689a333c6.js:13
captureSession @ 525-30b4f38689a333c6.js:13
_updateSessionFromEvent @ 525-30b4f38689a333c6.js:13
(anonymous) @ 525-30b4f38689a333c6.js:13
(anonymous) @ 525-30b4f38689a333c6.js:17
(anonymous) @ 525-30b4f38689a333c6.js:17
_executeHandlers @ 525-30b4f38689a333c6.js:17
(anonymous) @ 525-30b4f38689a333c6.js:17
s @ 525-30b4f38689a333c6.js:17
then @ 525-30b4f38689a333c6.js:17
_processEvent @ 525-30b4f38689a333c6.js:13
_captureEvent @ 525-30b4f38689a333c6.js:13
(anonymous) @ 525-30b4f38689a333c6.js:13
(anonymous) @ 525-30b4f38689a333c6.js:17
(anonymous) @ 525-30b4f38689a333c6.js:17
_executeHandlers @ 525-30b4f38689a333c6.js:17
(anonymous) @ 525-30b4f38689a333c6.js:17
s @ 525-30b4f38689a333c6.js:17
then @ 525-30b4f38689a333c6.js:17
captureException @ 525-30b4f38689a333c6.js:13
captureException @ 525-30b4f38689a333c6.js:2
l @ 525-30b4f38689a333c6.js:2
t @ global-error-1f760c5d859de6c8.js:1
oL @ efe33283-c38f5e3eb7da60e0.js:1
o5 @ efe33283-c38f5e3eb7da60e0.js:1
o8 @ efe33283-c38f5e3eb7da60e0.js:1
o5 @ efe33283-c38f5e3eb7da60e0.js:1
o8 @ efe33283-c38f5e3eb7da60e0.js:1
o5 @ efe33283-c38f5e3eb7da60e0.js:1
o8 @ efe33283-c38f5e3eb7da60e0.js:1
o5 @ efe33283-c38f5e3eb7da60e0.js:1
o8 @ efe33283-c38f5e3eb7da60e0.js:1
o5 @ efe33283-c38f5e3eb7da60e0.js:1
o8 @ efe33283-c38f5e3eb7da60e0.js:1
o5 @ efe33283-c38f5e3eb7da60e0.js:1
o8 @ efe33283-c38f5e3eb7da60e0.js:1
o5 @ efe33283-c38f5e3eb7da60e0.js:1
o8 @ efe33283-c38f5e3eb7da60e0.js:1
o5 @ efe33283-c38f5e3eb7da60e0.js:1
o8 @ efe33283-c38f5e3eb7da60e0.js:1
o5 @ efe33283-c38f5e3eb7da60e0.js:1
um @ efe33283-c38f5e3eb7da60e0.js:1
uD @ efe33283-c38f5e3eb7da60e0.js:1
uL @ efe33283-c38f5e3eb7da60e0.js:1
(anonymous) @ efe33283-c38f5e3eb7da60e0.js:1
ud @ efe33283-c38f5e3eb7da60e0.js:1
i8 @ efe33283-c38f5e3eb7da60e0.js:1
i3 @ efe33283-c38f5e3eb7da60e0.js:1
uF @ efe33283-c38f5e3eb7da60e0.js:1
T @ 525-30b4f38689a333c6.js:1
525-30b4f38689a333c6.js:16
POST https://o4508064544391168.ingest.de.sentry.io/api/4508064550551632/envelope/?sentry_key=09bfc307f1fd12228eadd7477e1656c8&sentry_version=7&sentry_client=sentry.javascript.nextjs%2F8.35.0 net::ERR_BLOCKED_BY_CLIENT
(anonymous) @ 525-30b4f38689a333c6.js:16
(anonymous) @ 525-30b4f38689a333c6.js:14
add @ 525-30b4f38689a333c6.js:14
send @ 525-30b4f38689a333c6.js:14
sendEnvelope @ 525-30b4f38689a333c6.js:13
sendEvent @ 525-30b4f38689a333c6.js:13
(anonymous) @ 525-30b4f38689a333c6.js:13
(anonymous) @ 525-30b4f38689a333c6.js:17
(anonymous) @ 525-30b4f38689a333c6.js:17
_executeHandlers @ 525-30b4f38689a333c6.js:17
(anonymous) @ 525-30b4f38689a333c6.js:17
s @ 525-30b4f38689a333c6.js:17
then @ 525-30b4f38689a333c6.js:17
_processEvent @ 525-30b4f38689a333c6.js:13
_captureEvent @ 525-30b4f38689a333c6.js:13
(anonymous) @ 525-30b4f38689a333c6.js:13
(anonymous) @ 525-30b4f38689a333c6.js:17
(anonymous) @ 525-30b4f38689a333c6.js:17
_executeHandlers @ 525-30b4f38689a333c6.js:17
(anonymous) @ 525-30b4f38689a333c6.js:17
s @ 525-30b4f38689a333c6.js:17
then @ 525-30b4f38689a333c6.js:17
captureException @ 525-30b4f38689a333c6.js:13
captureException @ 525-30b4f38689a333c6.js:2
l @ 525-30b4f38689a333c6.js:2
t @ global-error-1f760c5d859de6c8.js:1
oL @ efe33283-c38f5e3eb7da60e0.js:1
o5 @ efe33283-c38f5e3eb7da60e0.js:1
o8 @ efe33283-c38f5e3eb7da60e0.js:1
o5 @ efe33283-c38f5e3eb7da60e0.js:1
o8 @ efe33283-c38f5e3eb7da60e0.js:1
o5 @ efe33283-c38f5e3eb7da60e0.js:1
o8 @ efe33283-c38f5e3eb7da60e0.js:1
o5 @ efe33283-c38f5e3eb7da60e0.js:1
o8 @ efe33283-c38f5e3eb7da60e0.js:1
o5 @ efe33283-c38f5e3eb7da60e0.js:1
o8 @ efe33283-c38f5e3eb7da60e0.js:1
o5 @ efe33283-c38f5e3eb7da60e0.js:1
o8 @ efe33283-c38f5e3eb7da60e0.js:1
o5 @ efe33283-c38f5e3eb7da60e0.js:1
o8 @ efe33283-c38f5e3eb7da60e0.js:1
o5 @ efe33283-c38f5e3eb7da60e0.js:1
o8 @ efe33283-c38f5e3eb7da60e0.js:1
o5 @ efe33283-c38f5e3eb7da60e0.js:1
um @ efe33283-c38f5e3eb7da60e0.js:1
uD @ efe33283-c38f5e3eb7da60e0.js:1
uL @ efe33283-c38f5e3eb7da60e0.js:1
(anonymous) @ efe33283-c38f5e3eb7da60e0.js:1
ud @ efe33283-c38f5e3eb7da60e0.js:1
i8 @ efe33283-c38f5e3eb7da60e0.js:1
i3 @ efe33283-c38f5e3eb7da60e0.js:1
uF @ efe33283-c38f5e3eb7da60e0.js:1
T @ 525-30b4f38689a333c6.js:1
525-30b4f38689a333c6.js:16
The text was updated successfully, but these errors were encountered:
Thanks for your report, think our consumer is struggling at the moment so we're switching to jetstream as soon as we can. If you encounter this error your comment/post has likely suceeded but our consumer will not have picked it up yet so you won't be able to see it but it will get displayed eventually.
Along with that, we're also working on writing to our db before the PDS and then confirming that the record has been written as a future next step. Will keep you posted.
Describe the bug
Can't post comments due to a client-side exception. When attempting to submit a comment on any post, the action fails with the following error message:
Application error: a client-side exception has occurred (see the browser console for more information).
To Reproduce
Expected behavior
Comments should post successfully without any errors.
Screenshots
Desktop (please complete the following information):
Additional context
Log
The text was updated successfully, but these errors were encountered: