Updating model attribute using Amplify.API.Query about amplify-swift

[harsh62]

@ip5038 Thanks for raising the issue. Our team will look into the issue and provide an update as soon as we can.

[ip5038]

I wasn't able to find the fix for this issue, but the workaround to this is using a custom lambda conflict resolver. Add a custom lambda resolver via amplify cli and you can configure how you want to deal with conflicts. In my case, I just resolved the conflict without doing checks for versions or anything.

Amplify docs has information on how to setup custom lambda resolver.
This will also come in handy if you want to learn more about conflict resolutions including custom lambda resolutions: https://docs.aws.amazon.com/appsync/latest/devguide/conflict-detection-and-sync.html

[thisisabhash]

Hello, Do you know the Amplify version being used?
Latest version is 2.27.2 https://github.com/aws-amplify/amplify-swift/releases/tag/2.27.2

When you save the model after the update, are you seeing any errors being logged into the console? Are you able to receive .syncQueriesReady and .ready Datastore event? https://docs.amplify.aws/react/build-a-backend/more-features/datastore/datastore-events/#syncqueriesready

You can use
Amplify.Logging.logLevel = .verbose to enable verbose logging

It'd be great if you could attach the logs in the issue after removing sensitive information.