Harsh

@smediomike > when s3 uploading threads take more CPU and network, will impact app sync (local datastore -> server) Is this still only happening on the devices you mentioned "this...

@MrAsterisco Thanks for raising this issue. We recently released a new version [`2.48.1`](https://github.com/aws-amplify/amplify-swift/releases/tag/2.48.1) that has a fix to a subscription issue. Would you be able to update and validate if...

@MrAsterisco Thanks for the update. We'll wait for your findings from the newly released version. Keep us posted.

@RomanVolkov There have been a lot of changes between[ 2.29.0...2.49.0](https://github.com/aws-amplify/amplify-swift/compare/2.29.1...2.49.0). Meanwhile I investigate the logic that has caused this, is reverting back to the version that was working an option...

> we can try, especially if you can tell that it is okay to do downgrade. I don't see any issues downgrading. If you are using the Auth category, I...

@MrAsterisco Can you please share the following details to debug this further: * Configuration file redacted all the sensitive information * Code snippets of the Amplify usage in your project...

@MrAsterisco I think the error thrown here (`cognitoTokensError`) can be corrected by the Amplify team when you try to retrieve the user pool tokens. I don't think this would block...

> In our app, we react to other errors being thrown by Amplify to detect whether the user's session expired @MrAsterisco Would you be able to share the code snippet...

@MrAsterisco Thanks for the information, I will try to reproduce this locally and get back to you.

@MrAsterisco So I have been switching between previous and the latest version, your code would still slip into the default case. ``` switch authError { case .sessionExpired, .signedOut: ErrorReporter.reportError(authError, triggerBreakPoint:...