Dad, Runner, Entrepreneur and wanna be coder. I've been coding for fun for 30+ years. Jumping back in for fun learning React, Next, Tailwind and GraphQL.
Thank you for this. FYI my updateUser mutation was not working. After hours of trying to debug I found I had conflict detection turned on which seems to be what was causing issue so I ran amplify update api and went into additional settings and said No to conflict detection and that solved issue. Still not clear on what conflict detection does. :) Thanks!
Hope this helps someone else who runs into same issue
Sorry for barging in here, and it might be too late, but a conflict detection is used for DataStore if you want your application to work offline as well. So, when your app gets back online again, it synchronizes the data, and resolves potential conflicts.
Thank you for this. FYI my updateUser mutation was not working. After hours of trying to debug I found I had conflict detection turned on which seems to be what was causing issue so I ran amplify update api and went into additional settings and said No to conflict detection and that solved issue. Still not clear on what conflict detection does. :) Thanks!
Sorry for barging in here, and it might be too late, but a conflict detection is used for DataStore if you want your application to work offline as well. So, when your app gets back online again, it synchronizes the data, and resolves potential conflicts.
Reference: docs.amplify.aws/lib/datastore/con...