[BUG]: cannot drop function `storage.get_level(text)` because other objects depend on it

[Snehil-Shah]

Describe the bug
I'm not sure if this is the right repo to file this, but I get this error when running supabase after pulling all my schemas from my remote using supabase db pull --schema {all_my_schemas}.

To Reproduce
Steps to reproduce the behavior:

• Run supabase db pull.
• Run supabase db pull --schema auth,storage (as instructed).
• Reset the local instance to apply the migrations: supabase db reset.
• See error:

What I tried?
This issue was also posted here. And a reply pointed out to pull all schemas at once. (using the --schema flag).

Doing that made me realize #1840 hasn't been fixed yet? It doesn't actually pull the specified schemas on an empty migrations directory.

To temporarily fix this, I created and pushed an empty migration and reran supabase db pull --schema {all_of_my_schemas} and the pull worked, but it still gives the original error of cannot drop function storage.get_level(text) because other objects depend on it.

Expected behavior
All storage and auth policies should be pulled properly.

Screenshots

System information

• Ticket ID: bcf56a54d439409584c24af45f2b6cba
• Version of OS: Windows 11 (running using npx)
• Version of CLI: 2.20.12
• Version of Docker: 27.5.1
• Versions of services:

  SERVICE IMAGE          | LOCAL            | LINKED     
 ------------------------|------------------|------------
  supabase/postgres      | 15.8.1.040       | 15.8.1.040 
  supabase/gotrue        | v2.170.0         | v2.170.0   
  postgrest/postgrest    | v12.2.3          | v12.2.3    
  supabase/realtime      | v2.34.45         | -
  supabase/storage-api   | v1.19.3          | -
  supabase/edge-runtime  | v1.67.4          | -
  supabase/studio        | 20250317-6955350 | -
  supabase/postgres-meta | v0.88.2          | -
  supabase/logflare      | 1.12.0           | -
  supabase/supavisor     | 2.4.14           | -

Additional context

• Version of npx: 10.9.2

[willy20040711]

I have same issue. I recently update my supabase cli and try to sync remote auth, public, storage schema to local.
And follow few step

1. supabase db pull --schema public,auth,storage
2. supabase db dump --data-only > supabase/seed.sql
3. supabase db reset
   It seem fine in local db, but it will have same kind problems when try to sync back to remote(same pattern ex: If drop something, but that thing did not exist... )

[Snehil-Shah]

Closing as fixed in #3475, thanks to @sweatybridge!