-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Authentication issues #73
Comments
Thank you @Dragon863 for reporting. I am just back from vacation and checking in your issue shortly. |
Hi I am getting the same! Auth token always invalid. Any progress? |
Bump :) edit: I was facing the same issue while authenticating and using the token for creating a group. in session.dart
in nakama_grpc_client.dart
|
Token parsing issue and missing options fixed in next release (releasing today) |
Hi there! Thanks for the useful package, unfortunately I'm running into two issues. Firstly, the timestamps for the session expiry seem to be reported incorrectly (at some point in 1970), I believe this is because in
session.dart
fromMillisecondsSinceEpoch
is being called on the decoded token which stores the token in seconds since epoch. Whilst this can be worked around by changing the arguments to(token['exp'] as int) * 1000
in every line where this function is called in the file, I am still getting the message "Auth token invalid" when using any function with the session object (for example addFriends). I'm not sure if this is an issue with the package or the server I'm running, but I thought it could be relevant or maybe caused by the first issue.I used the official docs and logged using email and then attempted to add a friend to the account using the following:
This gives the following output:
After applying the fix I mentioned above the session is reported as expiring at the correct date, but the second error still occurs.
I am using flutter 3.13.0 and the latest version of this ibrary on pub.dev, and the latest docker image of nakama. Thank you in advance!
The text was updated successfully, but these errors were encountered: