No Callback for Auth.fetchUserAttributes #2170
Comments
AnilMaktala
added
auth
|
Thank you for your report. Someone on our team will take a look. |
|
Hi @tapovana-innovations can you paste the result of the fetchAuthSession after you are logged in before you do a fetchUserAttributes? Also if upgrading is an option for you I would highly recommend you to upgrade to V2 of the Amplify library for Android as we have rewritten it entirely in Kotlin. |
|
Hi 02/13 08:47:26: Launching 'app' on Xiaomi POCO F1. V/FA: onActivityCreated D/--- CLM ---: Configure Amplify D/AWSMobileClient: Using the SignInProviderConfig from D/--- CLM ---: Subscribe to Events D/AWSMobileClient: Inspecting user state details W/.tech.debu: Long monitor contention with owner Thread-6 (13096) at com.amazonaws.mobileconnectors.cognitoidentityprovider.CognitoUserSession com.amazonaws.mobileconnectors.cognitoidentityprovider.CognitoUser.readCachedTokens()(CognitoUser.java:2700) waiters=0 in com.amazonaws.mobileconnectors.cognitoidentityprovider.CognitoUserSession com.amazonaws.mobileconnectors.cognitoidentityprovider.CognitoUser.getCachedSession() for 1.321s |
|
In the properly working scenario this is the log 02/13 09:04:06: Launching 'app' on Xiaomi POCO F1. V/FA: onActivityCreated D/--- CLM ---: Configure Amplify D/AWSMobileClient: hasFederatedToken: false provider: cognito-idp.us-west-2.amazonaws.com/us-west-2_71D5Np1eQ D/AWSMobileClient: Inspecting user state details |
|
Thank you so much for providing this information. We will investigate and get back to you. |
|
HI @tapovana-innovations from what I understand the flow is this (Please correct me if I am wrong):
After #3 if you do a fetchAuthSession does it return a successful response with a successful user session? Is that correct? |
|
+1
We are using version 1.37.0 |
|
Sorry for delayed reply. The root of the issue appears to be lies in the Auth.fetchAuthSession which calls 'success' callback with 'success.isSignedIn' as TRUE though token/session is expired.. If it returns (when session is expired) 'FALSE' for 'isSignedIn' i guess that would guide developers to apply different logic in the code. We have tried to upgrade to 2.x but due to breaking changes we couldn't proceed. |
|
Already upgrade to 2.xx but this issue still unresolved Using version : 2.5.0 Anyone have a solution? |
|
@tapovana-innovations I have been able to reduce the scenario where fetchUserAttributes does not get called if the auth session is expired and unable to refresh due to refresh token expiration. @AnirudhWinimy You are reporting a different scenario of fetchAuthSession not returning a callback. I was unable to replicate the issue in the steps you have described. Could you please open a new issue for the issue that you are seeing with logs. @Androidbangnv Please open a new issue with logs, describing the scenario you are seeing. v1 and v2 of Amplify was a complete rewrite, so any logs posted for v1 issue do not translate to v2. |
|
From your 1st example showing no callback from When this event is fired, the refresh token has expired and the user must be logged out, and then signed in again. In the Amplify v1 implementation, there are a few methods like For Amplify v1, the expectation is that hub events are listened to, and the user is signed out upon receiving SESSION_EXPIRED. In Amplify v2, this behavior was changed, where From what I see in the logs, the v1 behavior is working as expected. |
|
Closing due to inactivity. Feel free to open a new issue if your problem still persists. |
|
Before opening, please confirm:
Language and Async Model
Kotlin
Amplify Categories
Authentication
Gradle script dependencies
Environment information
Please include any relevant guides or documentation you're referencing
No response
Describe the bug
No callback is received in app for Auth.fetchUserAttributes.
This is happening especially when the existing token in expired and user is re-authenticated.
We are using federated sign-in via OKTA. Login is successful and returned to app
App listens to Hub Events like this
Amplify.Hub.subscribe(
HubChannel.AUTH
) { hubEvent: HubEvent<*> -> ....
....
when (AuthChannelEventName.valueOf(hubEvent.name)) {
AuthChannelEventName.SIGNED_IN -> {
Auth.fetchUserAttributes(....
.....
Reproduction steps (if applicable)
User is re-authenticated as expected if token is expired and SIGNED_IN is notified at the app via Hub Events
When Auth.fetchUserAttributes is called no callback is returned
Code Snippet
// Put your code below this line.Log output
amplifyconfiguration.json
{
"auth": {
"plugins": {
"awsCognitoAuthPlugin": {
"IdentityManager": {
"Default": {}
},
"CredentialsProvider": {
"CognitoIdentity": {
"Default": {
"PoolId": "",
"Region": "us-west-2"
}
}
},
"CognitoUserPool": {
"Default": {
"PoolId": "",
"AppClientId": "5rtv8ahv2c7ijdlviqopsicas8",
"Region": "us-west-2"
}
},
"Auth": {
"Default": {
"OAuth": {
"WebDomain": ".auth.us-west-2.amazoncognito.com",
"AppClientId": "5rtv8ahv2c7ijdlviqopsicas8",
"SignInRedirectURI": "",
"SignOutRedirectURI": "",
"ResponseType": "code",
"Scopes": [
"phone",
"email",
"openid",
"profile",
"aws.cognito.signin.user.admin",
""
]
},
"authenticationFlowType": "USER_SRP_AUTH"
}
}
}
}
}
}
GraphQL Schema
Additional information and screenshots
No response
The text was updated successfully, but these errors were encountered: