Aaron S.

Anyone still facing this issue and need help troubleshooting?

Interesting. You've confirmed that PubSub/AWSIoTProvider is working as expected when not using AWSCloudWatchProvider, are you sure that AWSCloudWatchProvider is working when not using PubSub/AWSIoTProvider? From what you've said, I would...

With help from @jimblanc and @cwomack I was able to reproduce this problem. The PR to change the case didn't resolve the issue. Doing a bit more research, we identified...

The fix has been merged and released. To validate, I have upgraded my test app to `aws-amplify` 5.0.14 and `@aws-amplify/analytics` 6.0.14, which works without the error describe by this issue....

> When this will be published to main ? Today! --- Good news. Automated Reconnection is now available on the latest `aws-amplify` release! Review the [updated subscription docs](https://docs.amplify.aws/lib/graphqlapi/subscribe-data/q/platform/js/#connection-issues-and-automated-reconnection) and consider...

Hello @dylan-westbury, Correct that the reconnect changes were applied to Amplify and haven't been applied to the AppSync SDK. There are a few issues ([ex](https://github.com/awslabs/aws-mobile-appsync-sdk-js/issues/740)) on that package related to...

I am not aware of any work aimed to port reconnection back to the SDK package. I would recommend surfacing your need on one of the tickets that captures this...

Hello @raulgonzalezdev , From the comments above, it looks like your app was configured with `speechGenerator` and needs to be configured for `transcription` before it will work without the error...

Hi @alex-breen, The PR I closed above solved the problem, but introduced issues that could break expectations regarding how custom conflict resolution is handled. At this time we don't have...

Related to #9736