Dane Pilcher

I am still having difficulty reproducing the error unfortunately. Could you run `amplify diagnose --send-report` ([docs](https://docs.amplify.aws/cli/reference/diagnose/)) in your project and comment with the outputted ID.

Hi @chstrong, could you use the command [above](https://github.com/aws-amplify/amplify-js/issues/9179#issuecomment-1279139400) to help diagnose the issue.

I haven't created a ticket. I'll create one soon in [amplify-category-api](https://github.com/aws-amplify/amplify-category-api) and link back here.

I'll preface this by saying this is not supported use case of DataStore. The functionality could change at any time. @ArsSirek, I don't see any negative effects as it currently...

Seems to longer be an issue in the latest CLI. Please comment if you are still experiencing the issue.

I'm not able to reproduce this on the latest version. This bug must have been inadvertently fixed with some other change. Please comment if you are still experiencing the issue.

Custom primary key has been officially released. Please see our blog: https://aws.amazon.com/blogs/mobile/new-announcing-custom-primary-key-support-for-amplify-datastore/

Off the top of my head I can't think of a way, but I'll look into it further.

It appears that the issue is that the codegen step on `amplify pull` is happening even when the API category is not in use. Marking this as a bug.

I also think this fix would take place in the CLI repo, but I'm not sure. It will require some investigation.