Jon Wire

@chrisbonifacio Sorry if this was miscommunicated, but that PR doesn't doesn't solve this problem. It solves a problem with `.clear()` and `.stop()` that was interfering with the reproduction of this...

Looks related: https://github.com/aws-amplify/amplify-js/issues/5179

@dragosiordachioaia We're seeing this from at least one other customer as well. But, any additional information you can provide would be very helpful. Is there any chance you can provide...

@amitchaudhary140 The `@connection` directive in your model suggests you're using pretty old versions of the Amplify CLI and JS libraries. Per the article @undefobj linked, the lazy loading and nested...

The steps from my previous comment are intended to be run locally. Use the [`amplify pull`](https://docs.amplify.aws/cli/start/workflows/#amplify-pull) command if you don't already have your backend/schema pulled down to your local development...

The step that looks like it's missing from your list is `amplify migrate api`. I believe that's the command we designated to auto-migrate your schemas. After you run that, I...

Hey, it looks like you're trying to save updates on top of a record returned from `DataStore.save()`. Our guidance is to *always* re-query for the record using `DataStore.query()` before updating....

I've attempted to repro this to no avail. Are you seeing this at build time, or only in the IDE?

Are you using VS Code? If so, can you confirm VS Code is configured (or has recognized) the correct version of typescript? I'm having a hard time taking a screenshot...

Gotcha. Thanks for checking. Leaving in pending triage for @nadetastic to try to repro and/or ask followups.