Is supertokens_flutter production ready? Do you have some example repo?
u
Is supertokens_flutter production ready? Do you have some example repo?
r
hey @undesiredmonk it is production ready, however, we don't have any examples of it. But we do have detailed docs in the custom UI section.
u
The reason I asked is I'm trying to implement social login on Flutter. Found that your docs specified Comming soon. https://supertokens.com/docs/thirdpartypasswordless/custom-ui/thirdparty-login
Is social login not supported on flutter?
@rp_st
r
it is supported. You just need to figure out which lib to use in flutter to for the provider you are looking to integrate with. The curl commands shown will all work
u
Do you have it in priority to include these login strategies in the Flutter SDK itself anytime soon? If yes how long will it be?
r
we won't do that since those strategies come from other SDKs, built by the login providers (for example, google has their own native google login SDK for flutter)
u
Okay
I'm using google_sign_in for flutter. https://pub.dev/packages/google_sign_in. I'm bit confused on how to use this with supertokens. With google_sign_in I already have id_token and access_token. I don't have
code
value for
redirecURIInfo
. Should I add a new reciepe because I can slready sign in with google from my react app. Also I'm getting 404 for
<YOUR_API_DOMAIN>/auth/signinup
r
You can pass the id token or the access token to the backend as well. See more examples in the doc above
Can you enable backend debug logs and show the output when you call the api?
u
Backend logs
Copy code
[13:05:04 UTC] INFO: request completed
     reqId: "req-8"
     res: {
       "statusCode": 404
     }
     responseTime: 19.227292001247406
 [13:08:09 UTC] INFO: incoming request
     reqId: "req-9"
     req: {
       "method": "POST",
       "url": "/auth/signinup",
       "hostname": "localhost:20070",
       "remoteAddress": "127.0.0.1",
       "remotePort": 55439
     }
 [13:08:09 UTC] INFO: Route POST:/auth/signinup not found
     reqId: "req-9"
 [13:08:09 UTC] INFO: request completed
     reqId: "req-9"
     res: {
       "statusCode": 404
     }
     responseTime: 7.358792006969452
r
These aren’t our debug logs
Please see the troubleshooting section in the docs
u
This is the logs form docker.
r
not docker logs
backend sdk logs
please see our troubleshooting section in the docs
6 Views