Note: The current versions of staging and production are functioning properly. However, redeploying triggers the issue I’m encountering now. This doesn’t seem to be related to Supabase or any similar service, as an older version of the deployment works fine. Even with an empty commit (no code changes), simply redeploying causes the problem. I strongly suspect that something has changed during the build process or on Vercel’s hosting environment.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Login Page Stuck After Successful Auth | 2 | 50 | May 1, 2025 | |
| Error after auth using v0 deployment and supabase | 6 | 226 | March 7, 2025 | |
| Supabase session lost after new V0 preview or message | 1 | 36 | April 23, 2025 | |
| Build fails due to next/headers used in pages/ directory | 2 | 38 | April 21, 2025 | |
| Solved Bug: Authentication Redirect Issue in Sanicle-AI Platform | 1 | 26 | March 10, 2025 |