Mateusz Zagórski

Results 6 comments of Mateusz Zagórski

> > What we see from logs, most cases are for the users that were not using the application for quite some time, so that the access token is expired,...

Do you mean this one? ![Screenshot 2023-10-19 at 09 24 38](https://github.com/aws-amplify/aws-sdk-android/assets/4357770/8e3471f7-c5c7-40f4-8054-ba3a2c4a5bb4) As for the sign in type - I'm not sure which one is the most affected, but we're having...

Hey, we have `openid` set in scopes: `"Scopes": ["openid", "email", "profile"]` - and for the sign in method - we're using mostly the hosted (web) ui sign in flow (we...

Hello, so: - We do not have any sign-in capabilities that bypass the cognito flow - even if we are not using web hosted ui, we're relying on cognito methods...

@ankpshah Unfortunately we dont have full stacktrace - only the message from exception coming from cognito, I will check if we can change the logs so that we have full...

@ankpshah Here is the stacktrace we're getting: ``` Non-fatal Exception: java.lang.Exception: No cached session. at com.amazonaws.mobile.client.AWSMobileClient$11$1.signalTokensNotAvailable(AWSMobileClient.java:1968) at com.amazonaws.mobile.client.AWSMobileClient$11$1.getAuthenticationDetails(AWSMobileClient.java:1948) at com.amazonaws.mobileconnectors.cognitoidentityprovider.CognitoUser.getSession(CognitoUser.java:1032) at com.amazonaws.mobile.client.AWSMobileClient$11.run(AWSMobileClient.java:1929) at com.amazonaws.mobile.client.internal.InternalCallback$1.run(InternalCallback.java:101) at java.lang.Thread.run(Thread.java:923) ```