"Current session is missing data" when restoring a phone user

[chimon2000]

Bug report

Describe the bug

When attempting to restore the session, the user object is is returning null which causes the session to not be loaded.

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

1. Log in with a phone number user, using verifyOTP
2. Refresh the screen
3. Error should be printed when referencing recoverSession directly

Expected behavior

The user information should be returned when a user has successfully logged in using an SMS token. I noticed that this is not the case, when trying to print out the user info after a login, but I ignored it.

Screenshots

n/a

System information

• OS: Linux
• Browser (if applies): Chrome
• • Version of supabase: 0.1.0

Additional context

n/a

[bdlukaa]

Can you try to call SupabaseAuth.instance.auth.user?

[dshukertjr]

Thank you @chimon2000 for reporting this issue.

This bug seems to be related to supabase/auth#141, where upon verifying via OTP, user object is not being returned from the server.

[chimon2000]

Can you try to call SupabaseAuth.instance.auth.user?

When attempting to reference the user value either from the auth instance or the session it was coming back as null.

@bdlukaa

[dshukertjr]

@chimon2000
Yeah, this is not a bug on the client side, but on the server side. Unfortunately at the moment, it looks like we would have to wait for the issue on the server side to get resolved.

[neerajdana996]

any update on this ??

[dshukertjr]

@Neerajdana
This issue is cause by supabase/auth#141 so unfortunately no updates at the moment.

[bdlukaa]

supabase/auth#141 (comment)

[MisterJimson]

So based on the last comment linked above, should the Supabase clients internally call GET /user in verifyOTP so the users of the client libraries don't need to work around the issue?

[bdlukaa]

According to supabase/auth#141 (comment), #53 should fix this issue, no?

---

Edit: actually no. This issue is being caused because we check if the user is not null.

https://github.com/supabase-community/gotrue-dart/blob/main/lib/src/gotrue_client.dart#L315-L320

The same seems to happen in the js equivalent package:

https://github.com/supabase/gotrue-js/blob/master/src/GoTrueClient.ts#L635-L638

[bdlukaa]

It looks like this is back on the latest master:

I/flutter ( 9428): ***** Supabase init completed Instance of 'Supabase'
I/flutter ( 9428): Current session is missing data.