New Publishable API Keys vs. Legacy Anon Key
Hi Everyone
I have a web-app built that allows for certain authorized back-end users to write and insert directly into a certain supabase table.
Everything was working fine until yesterday, when I generated one of the new "publishable API keys".
- Not only did a simple copy-paste of the new API key into my .env file not work, but it also seems like it "broke" the "Legacy Public Anon Key" that was working correctly every day before then.
- Now no one is able to work with Supabase that isn't me (big problem)
I'm not sure what I might've missed in the support documents, but nothing seems to be helping.
An guidance is greatly appreciated.
I have a web-app built that allows for certain authorized back-end users to write and insert directly into a certain supabase table.
Everything was working fine until yesterday, when I generated one of the new "publishable API keys".
- Not only did a simple copy-paste of the new API key into my .env file not work, but it also seems like it "broke" the "Legacy Public Anon Key" that was working correctly every day before then.
- Now no one is able to work with Supabase that isn't me (big problem)
I'm not sure what I might've missed in the support documents, but nothing seems to be helping.
An guidance is greatly appreciated.
