canardos
canardos
I too experienced this issue when building. It is due to a gdb bug caused by the use of the internal-only API method `_PyImport_FixupBuiltin`. The signature of this method changed...
I can confirm this behavior, with `1.50.12` at least. It seems to be limited to triggers on tables in the `auth` schema. My application has two triggers on `auth.users` (on...
Are you using an older version of the local development environment? I was experiencing the same issue (local dev) and fixed it by upgrading to the latest CLI and local...
`Verify requires either a token or a token hash` is the [expected behavior](https://github.com/supabase/gotrue/blob/40aed622f24066b2718e4509a001026fe7d4b76d/internal/api/verify.go#L70C3-L72C4) when providing both the `token` and `token_hash`. I only had to provide both as I was using...
Apologies, but my earlier code had the wrong algo (I'm using node (`crypto.createHash("sha224").update(newEmail + otp).digest("hex").toLowerCase()`) and copied/adjusted for the browser). It [should be SHA-224](https://github.com/supabase/gotrue/blob/master/internal/crypto/crypto.go#L41). I don't think SHA-224 is supported...