supabase: Windows 10 and 11 supabase link is not working properly after scoop update vom supabase 1.69.(?) to 1.172.2

Bug report

  • I confirm this is a bug with Supabase, not with my own application.
  • I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

At windows 10 and 11 supabase link is not working properly after scoop update vom supabase 1.69.(?) to 1.172.2

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

  1. Make sure you have upgraded supabase to Version 1.172.2
  2. Call supabase link
  3. You will be prompted for your supabase remote postgres password. Provide it.
  4. The password is not accepted. (The username is auto-selected but not postgres as expected but postgres.XXX with XXX = supabase project name instead):

$ supabase link Selected project: XXX Enter your database password (or leave blank to skip): Connecting to remote database… failed to connect to postgres: failed to connect to host=aws-0-eu-central-1.pooler.supabase.com user=postgres.XXX database=postgres: failed SASL auth (invalid SCRAM server-final-message received from server)

With supabase version 1.69.X I confirmed that it worked. So it definitively changed meanwhile. I used cygwin and copy & pasted the password. Also the (really great) supase support confirmed that it does not work with windows 10 and powershell with copy & paste. Manually typing the password should work.

There are 2 possible workarounds with either setting the environment variable SUPABASE_DB_PASSWORD (which I did not tested) and using the password parameter and leaving the password prompt empty (which I tested):

supabase link --password YYY Selected project: XXX Enter your database password (or leave blank to skip): Finished supabase link.

Expected behavior

Providing the password when requested by the prompt should link the supabase remote database correctly.

System information

  • OS: Windows 10 & 11
  • Cygwin or Powershell
  • Version of supabase: 1.69.X (works), 1.172.2 (does not work)

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 1
  • Comments: 15 (7 by maintainers)

Most upvoted comments

I cannot repro with the latest versions on Mac or Linux so I’ll wait for someone from the CLI team to test/respond

@encima i tested it with windows 10 before updating to 1.172.2 and there it worked fine., after update it broke.

@encima also updating the just released newest version v1.176.2 does not help

@encima Thank you for the explanation 😃