-
Notifications
You must be signed in to change notification settings - Fork 203
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
FetchAuthSession error does not provide correct AuthError on refresh token expired #3496
Comments
@nonesc Thanks for opening the issue. Could you please provide (code snippets) how you are invoking the Please also provide |
Thanks for fast response @harsh62 Step would be
AmplifyManager.shared.fetchToken()
Here is amplifyConfiguration.json
Please let me know if you need more info. Thank you |
@nonesc This information is good.. Would you also be able to provide |
@nonesc I think I was able to understand whats causing this issue and created a fix for it. Would you be able to pull |
Morning @harsh62, It seems to work on my end. I received the followings after changing framework to
|
Thank you for confirming. I will work with my team to get a release out this week. |
@nonesc The fix has been released. Please use the latest version of Amplify. https://github.com/aws-amplify/amplify-swift/releases/tag/2.26.0. Thanks for your patience on this. |
|
Describe the bug
My Backend team set up token expiration as followings
FetchAuthSession error does not provide the correct AuthError when refresh token expired
Code I use at the moment
Reference that does not work: #3288
Steps To Reproduce
Expected behavior
FetchAuthSession should return AuthError as
.sessionExpired
Amplify Framework Version
2.25.6
Amplify Categories
Auth
Dependency manager
Swift PM
Swift version
5
CLI version
BE
Xcode version
15
Relevant log output
Is this a regression?
No
Regression additional context
No response
Platforms
iOS
OS Version
15
Device
iPhone 15
Specific to simulators
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: