In a project I'm developing, I use two Flutterflow applications using the same supabase project. I use the authentication feature in both projects. I found that when testing a project logged in a user, when testing the other project the user's authentication data is the same as the other application, they are conflicting, I found that this has to do with how supabase handles user sessions. This is only because I'm testing everything on the same machine, and therefore do tokens shuffle? Or should I really change my strategy? If so, how?
2 Flutterflow applications for a Supabase project
Integrations
Native authentication.
Yes
1
5 replies