Giuliano Turri

I have exactly the same problem. This is a very limiting problem because every time datastore tries to establish the connection and fails, we cannot catch and handle the SocketException....

Is there a workaround to catch WebSocket exceptions every time amplify retries to reconnect?

> Hi @giulitu95, the current best option available is to monitor the Hub events channel as described in this [docs page, #subscription-connection-status](https://docs.amplify.aws/gen1/flutter/build-a-backend/graphqlapi/subscribe-data/#subscription-connection-status). Thank you @Equartey, actually I don't need to...

Hello @tyllark, currently I cannot provide a minimal reproducible example. Many android users of my application reported this problem through the error tracking system I'm using (sentry). During the development...

I have identified the cause of the crash. One of my models includes a Float attribute, which is translated into a double in the generated Flutter model. The crash occurs...

Thank you @tyllark for your answer, I don't think that the crash or the freeze are expected behaviors of this library. In flutter a double value could be nan but...

After some tests I have discovered that network status events are correctly dispatched only after datastore tries to synchronize a model without internet connection. At this point a SocketException is...

Hi @ekjotmultani, I'm using a physical device (Samsung Galaxy S22). I have been able to reproduce the problem on a simple app calling the Amplify.DataStore.save() method in an infinite loop...

Thank you @NikaHsn. I forgot to mention that the problem is not related only to the save method, but if I alternate save with query methods the execution could get...

Is there any update on this issue? This bug makes it impossible to use selective sync, and I was wondering if there are any plans to address it. Thanks!