My team have been working on local supabase and suddenly things broke from 2.70.0 -> 2.70.1 - we are getting this error.
We've been trying to figure out what's going on; but haven't been able to get around it and have had to force downgrade to 2.70.0. 2.70.2 does not seem to fxi the issue as well.
The error is arising when the front-end attempts to make an authenticated call with an edge function. The front-end is still using "legacy" ANON keys rather than ACCESS/SECRET.. I expected there to be some sort of release notes or warning if things were moving from these legacy keys to the new key format.
Can anyone please advise on what we can do to fix our situation, besides wait for a fix? thank you