vercel / nextjs-subscription-payments

Clone, deploy, and fully customize a SaaS subscription application with Next.js.
https://subscription-payments.vercel.app/
MIT License
5.77k stars 1.18k forks source link

Vercel Deploy Button setup process broken #306

Closed Hahlh closed 4 months ago

Hahlh commented 4 months ago

I really don't know whether I am alone with this. But for me at least, I need to try 10 times before I get this project even just "up" using the Vercel button (edit: I can't seem to get it up with the deploy button at all anymore).

One big reason for the frustrating nature of the process is that the process isn't atomic and that I constantly need to either delete the Github repo or the Supabase project or the Vercel Project or the Vercel integration to delete the Supabase project if something goes wrong.

Which it does a lot. At least for me.

Failed to sync environment variables: {"error":{"code":"not_found","message":"Project not found."}}

And when the process goes wrong again, I need to go in and delete that Github repo again, because it isn't possible to select an existing repo:

The specified name is already used for a different Git repository. Please enter a new one.

Type the project name, 2FA, get it deleted.

The tables haven't been created? Okay, so I guess I need as well to delete the Supabase project to being able to set this up again.

Failed to delete project: The project currently has active integration connections. Kindly delete the existing connections and try again.

Ah, I can't delete it until the Vercel integration from that project that has automatically been created is deleted?

So lets head over to the project settings and do that. Go back to the deploy button, try it again.

Failed to sync environment variables: {"error":{"code":"not_found","message":"Project not found."}}

Github repo gets created, Supabase project with integration was created again. Vercel project was created again. Cycle repeats.

For Github - after the manual deletion of the repo created by Vercel - it actually seems Vercel is sometimes first creating the repo, but still thinks the repo already exists. Stale state?

(Edit while finishing writing this. Now I can't seem to get it done at all. Every single time I delete the project and then try to restart the process, Vercel first creates the project (I can see it happening) and then tells me that the repo already exists. Even after closing the tab completely and reopening. Changed the project name, now it seems to work again.)

For the moment I seem to be unable to get the template running at all using the deploy button.

So I will revert to the manual setup process and hope that goes smoothly. Potentially somebody else can confirm if they are also experiencing such issues, I hope this issue helps or is at least interesting from a DX perspective regarding the Vercel deploy button process in general.

Potentially related to #298.

Hahlh commented 4 months ago

It seems to have gone through now, I am not entirely certain what made the difference. Potentially selecting to generate the seed example tables as well?