Skip to content
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

deepdish:connect errors with token expiry. #755

Open
saeelparsekar-aa opened this issue Sep 19, 2023 · 0 comments
Open

deepdish:connect errors with token expiry. #755

saeelparsekar-aa opened this issue Sep 19, 2023 · 0 comments

Comments

@saeelparsekar-aa
Copy link

Note: If your issue/feature-request/question is regarding the AWS AppSync service, please log it in the
official AWS AppSync forum

Bug

We have a app which has its subscriptions through appsync library version ^4.1.9. It has a authentication mechanism set to AWS Lambda. so it basically uses the Access Token from session storage of the web app. We renew the token every 1 hour so basically UI always have the valid token in session storage. However we see a sudden logs in the backend where appsync sends a expired token in a method called deepdish:connect. This token is not the latest one and hence a error is logged as expired token. However after this one fail next request which goes it passes successfully as the expired token is dumped and new token is taken.

We expect that everytime the library internally tris to connect or make a deepdish:connect call, it should use the latest token rather than expired one. We have that available in sessionStorage all the time

@saeelparsekar-aa saeelparsekar-aa changed the title deepdish:connect errors whn library tries reconnect on its own deepdish:connect errors with token expiry. Sep 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant