poojamat

Push notification to achieve your use case will be better strategy.

Did you disable the subscription as well? What was your mechanism to disable mutation?

@liyang15515 could you please retry the save without supplying the id to the post builder? Let ID be autogenerated.

I am sorry that you are still facing this issue. Could you please elaborate on what kind of associations does your model types have in the schema?

@shri-onecup sorry to hear that you are still facing this issue. We are unable to reproduce this error on our side. Could you please file a report [here](https://docs.amplify.aws/cli/reference/diagnose/)? That way...

@joekiller thanks for all the useful data and suggestions, we are reviewing this internally.

When you start datastore sync starts in the background. You can use the [observe query API](https://docs.amplify.aws/lib/datastore/real-time/q/platform/android/#observe-query-results-in-real-time) to get the realtime sync results and you will be notified when sync is...

Is there any data saved locally when the app is started?

The data coming back from the sync query is ordered only by the hash key. Unfortunately we do not support specific sort during the sync operation. I will add this...

Unfortunately there is no way to set this time out at this time. We will put this is a feature request as well.