Tyler-Larkin

Hello @dagovalsusa, thank for running the additional logging, but it looks like we only have the original error message for the time being: >Unable to establish connection on channel: "dev.flutter.pigeon.amplify_secure_storage.AmplifySecureStoragePigeon.read"`...

@dagovalsusa I'm glad you found a solution! I was still unable to reproduce the issue in release mode, so I think your theory that a conflict with another dependency might...

Hello @angelorodem, thanks for taking the time to open this feature request. I think this is a good suggestion that would enable quality of life features for customers. While we...

Hello @angelorodem, unfortunately we do not have an ETA at this time. When we do have an update we will post here.

Hello @angelorodem, thank you for the PR with a detailed explanation! I will review with the team and get back to you!

Hello @angelorodem, sorry for the delay. I scheduled a meeting with the team to review the public API changes. I will post any feedback on the PR afterwards.

Hello @angelorodem [Amplify Authenticator 2.4.0](https://pub.dev/packages/amplify_authenticator) was just launched with this feature. We appreciate all the hard work you put into the PR and I think it is a great addition...

Hello @matta-pie, thanks for taking the time to open this issue. We will keep this open as a feature parity request, please give your description a thumbs to help us...

Hello @matta-pie, I used an API key to test the following code, but you should be able to update the authorization mapping to match you preferred subprotocol format as documented...

Hello @abarone-btf, for production frontend code I recommend using authorization rather than an API key, which you can read more about [here](https://docs.aws.amazon.com/appsync/latest/eventapi/event-api-websocket-protocol.html). The code snippet I provided is only intended...