Supabase server refusing to start locally because of migrations mismatch

I am new to supabase I need help starting my supabase server locally

I'm working on a project that was initially started with Lovable AI and uses Supabase as it's backend. I recently joined the team and I'm trying to make backend changes with Supabase locally. after cloning the repo, installing Supabase and linking the project, I ran

supabase Start

supabase Start

however, the sever stopped because one of the migrations in my migrations folder caused an issue. I tried running

supabase db pull --linked

supabase db pull --linked

to get the updated version of the migrations folder, yet that is failing too, I'm getting an error

The remote database's migration history does not match local files in supabase\migrations directory.

The remote database's migration history does not match local files in supabase\migrations directory.

I did some ChatGPT digging, the issue seems happen because Lovable updates the database directly without notifying to supabase remote that the migrations are getting applied therefore when I try to run

supabase db pull --linked

supabase db pull --linked

supabase cannot find remote hash for those migrations and it causes mismatch errors. The only option I have it seems is to delete every row in the migration history table then

run db pull

run db pull

for my migrations to update. needless to say that I don't wanna do that since I'm incurring the risk of loosing migrations information for the whole team, and how that would affect our supabase server and it's Lovable integration.

My project project configuration :

React - Typescript for Frontend
Supabase Backend

environement:

Windows 11
Vscode

I installed supabase through Scoop

My question is how can I successfully run supabase

db pull --linked

db pull --linked

without having to clear my migrations history table ? and how can I approach developing with Supabase locally while sharing an environment with Lovable ?

Supabase server refusing to start locally because of migrations mismatch

supabase Start

supabase Start

however, the sever stopped because one of the migrations in my migrations folder caused an issue. I tried running

supabase db pull --linked

supabase db pull --linked

to get the updated version of the migrations folder, yet that is failing too, I'm getting an error

The remote database's migration history does not match local files in supabase\migrations directory.

The remote database's migration history does not match local files in supabase\migrations directory.

supabase db pull --linked

supabase db pull --linked

supabase cannot find remote hash for those migrations and it causes mismatch errors. The only option I have it seems is to delete every row in the migration history table then

run db pull

run db pull

db pull --linked

db pull --linked

without having to clear my migrations history table ? and how can I approach developing with Supabase locally while sharing an environment with Lovable ?

Supabase server refusing to start locally because of migrations mismatch

Supabase server refusing to start locally because of migrations mismatch

Similar Threads

Similar Threads

Similar Threads