Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Account Settings Email Page Suspense Issue #335

Open
ralf-boltshauser opened this issue Nov 8, 2024 · 4 comments
Open

Account Settings Email Page Suspense Issue #335

ralf-boltshauser opened this issue Nov 8, 2024 · 4 comments
Assignees

Comments

@ralf-boltshauser
Copy link

ralf-boltshauser commented Nov 8, 2024

In the Account Settings handler, when switching to the email tab, the nav is gone because a suspense boundary is triggered on level too high. (That's at least my assumption of how it looks)

@N2D4
Copy link
Contributor

N2D4 commented Nov 15, 2024

Do you want to work on this? @ralf-boltshauser

@ralf-boltshauser
Copy link
Author

yes sure, currently I am actually debugging some bigger issue that actually might be related to stack-auth and be the fundament of this. I will come back later and maybe delete / merge this issue into the larger thing.

I figured out, that in stack-auth projects (need to confirm) when I execute a server action the loading.tsx is retriggered. Whereas in normal nextjs applications the loading.tsx only triggered in the first render and then afterwards it just updates the state.

As soon as I have narrowed down that thing I will update the issue and take a look at it!

@fomalhautb
Copy link
Contributor

fomalhautb commented Nov 15, 2024

yes sure, currently I am actually debugging some bigger issue that actually might be related to stack-auth and be the fundament of this. I will come back later and maybe delete / merge this issue into the larger thing.

I figured out, that in stack-auth projects (need to confirm) when I execute a server action the loading.tsx is retriggered. Whereas in normal nextjs applications the loading.tsx only triggered in the first render and then afterwards it just updates the state.

As soon as I have narrowed down that thing I will update the issue and take a look at it!

This might be because of this vercel/next.js#50163

Next.js 14 automatically refreshes the page when setting cookies in server actions. However, based on my testing, Next.js 15 doesn't seem to have this problem. So, if it is not too hard, you can upgrade to Next.js 15, and the problem should be solved. We will also probably try to come up with something to workaround this, like disabling cookies in server action.

@ralf-boltshauser
Copy link
Author

ahh I see thank you, I will give it a shot!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants