ZEVA2 - useTransition stuck in loading state when using router.refresh() after calling a server action
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 6
- Avg merge
- 8h 52m
- Merged PRs (30d)
- 33
Description
**Describe the Bug**
Please see: https://github.com/vercel/next.js/issues/86055
**Expected Behaviour**
Please see: https://github.com/vercel/next.js/issues/86055
**Actual Behaviour**
Please see: https://github.com/vercel/next.js/issues/86055
**Implications**
Please see: https://github.com/vercel/next.js/issues/86055
**Steps To Reproduce**
Please see: https://github.com/vercel/next.js/issues/86055
**Remarks**
(1) A supplier user can sometimes experience the issue linked above when they submit a CA.
(2) Based on the discussion in the link above, we can expect this issue to be resolved in version 16.3.0 of nextjs.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the linked Next.js issue 86055 and reproduce the problem during a supplier CA submission. Focus on the server action, router.refresh(), and useTransition loading state; done means the transition no longer remains stuck, including after the expected Next.js 16.3.0 resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100