Datastore conflict AutoMerge behaves differently from amplify-android

[HuiSF]

Describe the bug

Original issue amplify-flutter #634

amplify-ios AutoMerge for handling conflict caused by multi-device offline/online syncing behaves differently from amplify-android, where amplify-android seems having the correct behavior.

Detailed description please refer to this comment

Steps To Reproduce

Steps to reproduce the behavior:
1. Run datastore in two iOS simulators, say device A and device B, both have same data
2. Make device A and B both offline
3. Make changes to a piece of data in device A, quit App, then make device A online, reopen the App to publish the update mutation
4. Make changes to the same piece of data in device B, quit App, then make device B online, reopen the App to publish the update mutation

Expected behavior

The update mutation made in device B when it was offline should be merged into DynamoDB after AutoMerge

Amplify Framework Version

1.11.0

Amplify Categories

DataStore

Dependency manager

Cocoapods

Swift version

5

CLI version

5.1.0

Xcode version

12.5.1

Relevant log output

No response

Is this a regression? (i.e. was this working before a version upgrade)

No response

Device

iPhone 12 simulators

iOS Version

iOS 14.5

Specific to simulators

No response

Additional context

No response

[HuiSF]

@lawmicha any update on this issue please?

[chrisbonifacio]

@HuiSF sorry the delay, we've triaged the issue and added it to our backlog for improving behavior parity between platforms.

[atierian]

This fix has been released in 2.25.3 and 1.30.6

Thanks for reporting this and for your patience!

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.