Tyler-Larkin

Hello @naveenthontepu, unfortunately we do not have any updates or a timeline currently. With [Pinpoint announcing end of support](https://docs.aws.amazon.com/pinpoint/latest/userguide/migrate.html) we will have to make some major changes to our push...

Hello @dagovalsusa we bumped web_socket_channel to ^3.0.3 in this [PR](https://github.com/aws-amplify/amplify-flutter/pull/6165), which will be included in the next release!

Hello @dagovalsusa, the fix for this was just released in Amplify Flutter 2.6.4. Please let us know if this resolved your issue!

Hello @sk92129, I'm glad we could resolve the issue! Both the [Flutter](https://docs.flutter.dev/data-and-backend/networking#android) and [Android](https://developer.android.com/develop/connectivity/network-ops/connecting) networking documentation indicate that this permission is required to access the internet, so I'm surprised any...

Hello @Kam5678, thanks for taking the time to reach out. I'm trying to replicate your backend, but the schema is missing some type definitions. Could you please provide the rest...

Hello @Kam5678, I'm looking into a method for sending the schema in a secure manner. In the meantime I've been trying to reproduce the issue with a simplified versions of...

Hello @Kam5678, sorry for the delayed response. Flutter doesn't implement DataStore itself, instead we wrap the Amplify Swift/Android DataStore implementations, which can lead to some discrepancies between the platforms. -...

Hello @Kam5678, thank you for providing the schema, I've been able to reproduce the issue on my side. The performance hit seems to be related to saving/querying types with nested...

Hello @Kam5678, The Amplify Swift team was able to reproduce the issue on their side, so I've created an [issue](https://github.com/aws-amplify/amplify-swift/issues/4016) in their repository. Once they have a fix we will...

Hello @dagovalsusa, I've been unable to reproduce the issue after copying your `settings.gradle`, `gradle distribution`, `gradle.properties`, and `proguard-rules.pro`. Can you please add the following error handling with print statements to...