-
Notifications
You must be signed in to change notification settings - Fork 200
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
AuthError: Service error #3910
Comments
Hi @micaeloliveira-void , thanks for reaching out. Could you please provide the verbose logs when this issue happens? That might provide additional information. You can enable verbose logging by adding: Amplify.Logging.logLevel = .verbose before calling Thanks! |
Thank you for the fast reply :) |
@micaeloliveira-void Are you still seeing this error and able to grab verbose logs? |
Thank you for contacting us.
This is very difficult to replicate as we haven't found anything that is related/causes this problem.
|
Describe the bug
We are verifying some occurrences of AuthError: Service error.
We started facing this problem on version 2.35.3 of Amplify-ios and after updated to version 2.43.0 this is still happening.
When opening the app and dealing with the normal behavior for Auth Services (the
fetchAuthSession
) we sometimes get a Service Auth Error.We also noticed this error occurring with the Logout (the
signOut
), even thought the Logout works as it should we sometimes get this error.Steps To Reproduce
Expected behavior
As expected behavior we shouldn't get a Service Auth Error.
Amplify Framework Version
2.43.0
Amplify Categories
Auth
Dependency manager
Swift PM
Swift version
5.10
CLI version
Xcode version
15.4 and also 16.0
Relevant log output
Is this a regression?
No
Regression additional context
No response
Platforms
iOS
OS Version
Logs for >= iOS 16.7.10
Device
Logs for iPhone 8, X, 12, 12 Pro
Specific to simulators
No response
Additional context
We have some Logs retrieving this:
Get access token failed with error: AuthError: Service error occurred
Recovery suggestion: There is a possibility that there is a bug if this error persists. Please take a look at https://github.com/aws-amplify/amplify-ios/issues to see if there are any existing issues that match your scenario, and file an issue with the details of the bug if there isn't.
The text was updated successfully, but these errors were encountered: