"Cannot use 'in' operator to search for 'name' in null" during Amplify Codegen @aws-amplify/cli @12.7.0

[ObinnaAka]

How did you install the Amplify CLI?

pnpm

If applicable, what version of Node.js are you using?

20.7.0

Amplify CLI Version

12.7.0

What operating system are you using?

Ma

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

No manual changes made

Describe the bug

When running amplify codegen, i get the following output

amplify codegen ✔ Generated GraphQL operations successfully and saved at graphql ✖ Cannot use 'in' operator to search for 'name' in null

When I downgrade to @aws-amplify/[email protected] it works

Expected behavior

✔ Generated GraphQL operations successfully and saved at graphql ✔ Code generated successfully and saved in file api/API.ts

Reproduction steps

Run amplify codegen. I cannot identify if any change to the schema led to this.

Project Identifier

a1fad6e952abc1a3b581c4d3442702d2

Log output

# Put your logs below this line

✖ Cannot use 'in' operator to search for 'name' in null

Additional information

After downgrading to v11.1.1 then upgrading back to 12.7.0 it now works as intended.

Before submitting, please confirm:

• I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
• I have removed any sensitive information from my code snippets and submission.

[ykethan]

Hey @ObinnaAka, thank you for reaching out. The issue appears to be similar to aws-amplify/amplify-codegen#734. additionally, a fix has been merged here:aws-amplify/amplify-codegen#738 and should be released in the upcoming updates.

A workaround on the comment aws-amplify/amplify-codegen#734 (comment) seems to mitigate the issue; which suggests adding API.ts as an exclusion in the .graphqlconfig.yml file.

[jgo80]

Same for me. I fear downgrading to v11 will kill my project. Please fix 12.7 🙏

[ykethan]

Closing the issue as the PR has been merged. please feel free in reaching out to us if the issue reoccurs.

[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.