Anonymous account does not have permission on schema "public" despite having valid JWT with "authenticated" role

[evelant]

Bug report

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

Describe the bug

I'm transitioning my app from firebase auth to supabase auth. When I use signInAnonymously() the client gets a valid JWT with the authenticated role but all calls to the database fail with permission denied for schema public

To Reproduce

1. await supabase.auth.signInAnonymously()
2. await supabase.from("table_name").insert(data)

Expected behavior

Anonymously authenticated users should have the same access to schemas as normally authenticated users

Screenshots

System information

• OS: macos
• Browser (if applies) N/A
• Version of supabase-js: 2.43.2
• Version of supabase-cli: 1.167.4
• Version of Node.js: N/A

Additional context

Looking at the schema of my local db authenticated has usage permission on public so I'm not sure why I'm getting permission denied

[evelant]

Hmm OK it turns out that the session is disappearing from the client for some reason. I have a singleton client but somehow shortly after anonymous sign in the session disappears.

[evelant]

🤦 nevermind. I was clearing my mmkv instance (local storage) as part of my new user setup flow. Now that supabase auth is stored in local storage it cleared the session.