incomplete-app-router-transaction

[chukusuccess]

what does this error mean? it's caught by sentry when a sign-in attempt is made by some users and i can't make much sense of it. Also i have tried to upload source maps so i can see the bad code but I get this "Missing Source Context" error on sentry. Is this a NextJs 14.2.7 issue? I need some help, suggestions, and answers please.🙏

[aldenquimby]

@chukusuccess are you using Clerk for auth? We are seeing the same problem after Clerk sign in, with the same unhelpful Sentry log. The app hard crashes for users when this happens. Wondering if it may be a Clerk bug

[aldenquimby]

@DawnMD we use Sentry for error monitoring, and it has a replays feature where you can watch user sessions. Every time this error happens, users land on our "app hard crashed" page

[DawnMD]

@aldenquimby Hmm, interesting. For me it's not crashing the page. Or might by our sentry not catching the latest replays as quota is not available. Let see if we can replicate the same in local!

[jescalan]

👀 clerk employee, we're looking into this one

[elie222]

I'm facing the same issue, but not using Clerk. Hard crash as well.

[elie222]

@jescalan
Did you figure out the issue for Clerk? Facing this issue too, but can't find the root of it

[chukusuccess]

@aldenquimby @DawnMD @martingalovic Sorry for the late response, been caught up with work but I was able to debug my issue. In my case the data that was supposed to be passed into the dashboard component after sign-in was sometimes incomplete (especially image links) so the navigation from sign-in page into the dashboard was breaking. After doing proper checks for data before rendering anything (especially Image tags), I stopped seeing the error on sentry. @aldenquimby I'm not using Clerk for auth in my project but you should check for the presence of data in the page you are routing to and see if that helps with the "incomplete" routing bug.

[DawnMD]

I was suspecting the same thing. But how do you differentiate when the images or maybe some fetch done loading?

[aldenquimby]

@chukusuccess could you give a rough before/after example of your next Image usage showing what the problem was and how you fixed it?

I appreciate the tip. I am seeing this when redirecting from Clerk sign-in to a dozen other pages, so I suspect I have a different problem, but am investigating.

[elie222]

Any updates here? This has been a major issue for us and just can't find a fix for it. Our issue isn't Clerk related.

[lilly-lumosity]

Also running into this issue- using Firebase for auth. Hard to recreate (have been unable to repro locally) but happens at least once a day in prod. Usually comes with sentry message "Unexpected end of input" or "Invalid or unexpected token", though breadcrumbs show 200 responses. We have been telling users to log in with an incognito browser if they get the hard crash which seems to solve it, but not sure if it is actually 'solving' it or is just a transient issue.

Using next version 13.4.10 if relevant. Tried switching from router.push() to router.replace() when navigating from login to home page, but still seeing the issue.

Going to take a look at the proper checks for data rendering/image tags solution mentioned above, but would appreciate any other insight.

[djshubs]

we aren't using clerk, but we are seeing this being reported a lot on Sentry as well.

I haven't validated why its happening for us, but my gut reaction is that when we're redirecting or pushing people to notFound() function that it causes this issue.

My understanding is that the redirect and notFound() functions in nextjs are "throwing an error" which terminates the rendering.

Any help or workaround would be appreciated.

[elie222]

There are other GitHub issues open around redirect throwing an error. Sentry handles it fine. It's not related to this issue.

[ozandalgali]

I am using Supabase yet also experiencing this issue on production, especially on some Android 10 devices, the points we use router hook we get this error often at least twice a day. I think I will leave router once and for all build separate pages for every route.

[ryananhtuan-nguyen]

Has anyone figured out what the issue is yet? I'm using Clerk and Supabase all together but those dont seem to be related to the issues.
This error only show up in Sentry, have not been able to reprod in local.

[elie222]

Nope. Would love some feedback on this issue too :(

[justman00]

same thing here, completely in the dark with this one

[ryananhtuan-nguyen]

How did you guys sending error to sentry? With a global-error.tsx file?
The incomplete-app-router-transaction for me comming from errors that not handled by the error.tsx file (so it is not just one but multiple error that referencing the same name "incomplete-app-router-transaction"). These errors for my case dont send users to the hard crash page (app is still functioning) but throwing error behind the scene. So I figure it has nothing to do with the error.

[albertocubeddu]

Any update? Just got the error for the first time;
The change we've done is adding a UseContext in the page.

[ariannargesi]

Same issue here