Guilherme Souza
Guilherme Souza
Hi @EduardMe do you have any extension also using Supabase? Widgets...
Thanks @EduardMe I'm investigating it, and will post any updates I find on this issue.
@LucasAbijmil which version were you using before, which you wasn't having this issue?
@EduardMe I don't think that is causing the issue, but your check is redundant, when you call the `try await supabase.auth.session` it already validates if session is expired, if it...
Hi @randalllex-collab, The refresh token isn't truncated. 12 chars of length is the correct size of the refresh token. Did you try to use it to restore a session using...
I believe this might be connected to the issue at https://github.com/supabase/supabase-swift/issues/753. There seems to be an error in the logic for removing the session when an error occurs. I’ll look...
Hi, thanks for reporting this, indeed it is a side effect of not using the same URLSession, but this is also considered a bug, as there is a workaround I...
@bbauman1 thanks for trying that commit. > Not sure if I am supposed to be holding onto the jwt in keychain myself or prompting any refreshes on my own before...
@bbauman1 as a workaround, you can manually update functions's auth info before calling your edge function, as: ```swift let accessToken = try await supabase.auth.session.accessToken supabase.functions.setAuth(accessToken) // Make sure to `setAuth`...
This fix unfortunately isn't as straight forward as I first imagined, that is one of the main reasons why the method is still marked as experimental, the way networking layer...