This repository has been archived by the owner on Jan 23, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Automatic deployment fails during Supabase Integration #370
Comments
Same problem here |
same problem here too |
Same problem |
I came across this video, which is very helpful, though it assumes the automatic deployment was successful: https://www.youtube.com/watch?v=I7CFD99sp1g Reading the comments, one can see that there are a few users who ran into the automatic deployment issue, so it looks like this one has been around for at least 4-5 months. Comments like "the template is broken in so many places. Supabase code needs to be updated..." Hopefully someone from Vercel will get around to fixing this. |
doesnt work |
Same, get error when adding integration and can't proceed |
+1 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have tried a couple of automatic deployment approaches and run into issues both times. The docs allude to failures in the process so I guess it isn't that surprising, but I thought it worth detailing what I discovered in case there is something simple I'm missing.
In the first case, I'm using a Supabase organization that is "Managed by Vercel Marketplace" with the "Pro" plan and my credit card data stored on the Vercel side for the Supabase usage. When I get to the "New Project" modal and enter the project name and generate a DB password, I immediately get a status message that says "Project creation for this Vercel managed distribution is disabled in the Supabase dashboard”.
I don't see an obvious place to "enable project creation". I do see that on the Vercel side both Read & Write" are checked:
My second approach was to try and use an unmanaged Supabase Org that I set up myself. In this case things proceeded a bit further - I see a status message that says “Done fetching initial migrations”) but then it says “Could not sync environment variables..project not found.”
I do notice that on the Supabase side the project is still "coming up". Perhaps this is why things can't sync?
Any insights appreciated!
The text was updated successfully, but these errors were encountered: