Ankit Shah

Apologies for the delay @ashibuth. @hassanctech, please take a look at this.

@m-zagorski is it possible for you to provide detailed logs/stacktrace with sensitive information obfuscated? It would be helpful to understand under what condition no cached session messages are being logged...

Hello @m-zagorski, Could you upgrade to AWS Android SDK [v2.75.0](https://github.com/aws-amplify/aws-sdk-android/releases/tag/release_v2.75.0) which provides a clear message during getTokens when there are no valid tokens on device. When doing so, please make...

Thanks for reporting the issue. I have following questions: 1. How much time does it take for SDK to report failure and how much time does device take to detect...

Hello, We will try to replicate this issue. Meanwhile to ensure that this doesn't block users facing this issue, I can suggest implementing custom timeout handling in your application. This...

Hello, I was not able to replicate this behavior. Following is the setup I used to replicate this scenario: 1. I used Proxy and set the bandwidth to 0 kbps...

As mentioned by Tyler you need to use: `mqttManager.connect(AWSMobileClient.getInstance()....` More Details [here](https://docs.amplify.aws/sdk/pubsub/working-api/q/platform/android/#aws-credentials-based-authentication) Let us know if you are still facing the issue

Hello, I am unable to replicate this issue. Could you try upgrading your Kotlin version to 1.8.0+ and check if issue persists?

Hello, @sayasheng. can you upgrade to latest version of Amplify [v2.14.11](https://github.com/aws-amplify/amplify-android/releases/tag/release_v2.14.11)? Latest release has fix for adding fallback logic for corrupt keys to EncryptedKeyValueRepository.

Hello @sayasheng, I tried replicating this issue by signing in using v1 (v1.38.8) then upgraded to v2 (v2.14.11). Followed by Sign out and Sign In operation using v2. I was...