amplify push fails with Zlib error after amplify add function

[pr0g]

How did you install the Amplify CLI?

npm

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

16.20.2

Amplify CLI Version

12.10.1

What operating system are you using?

Mac (Sonama 14.2.1)

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

N/A

Describe the bug

When attempting to run amplify push after previously adding a new lambda function (amplify add function <name>) after the GraphQL schema is compiled, I receive an error that looks roughly like the following:

Received error [Error: Command failed with exit code 1: yarn --no-bin-links --production
...
error Error: incorrect data check
    at Zlib.zlibOnError [as onerror] (node:zlib:189:17)
yarn install v1.22.21
info No lockfile found.
[1/4] Resolving packages...
[2/4] Fetching packages...
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.] running command [yarn --no-bin-links --production]

I did some searching to see if anyone else has reported this and I came across this Stack Overflow post that seems to indicate it may be related to macOS Sonama (which I'm running).

I performed the exact same operation on a different machine running Windows 11, and things worked as expected.

If you have any idea what this may be or how I could resolve I'd be very grateful to know.

Expected behavior

amplify push works as expected on macOS Sonama when trying to add a new function

Reproduction steps

Not currently available - If more information is required I can try to reproduce in a smaller project

Project Identifier

1da990300fc92aec89645b7f0ce67ae3

Log output

This is a snippet from the log

2024-02-27T12:02:31.836Z|error : Received error [Error: Command failed with exit code 1: yarn --no-bin-links --production
warning <app> > aws-appsync > [email protected]: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
warning <app> > aws-appsync-auth-link > @aws-sdk/[email protected]: This package has moved to @smithy/util-hex-encoding
warning <app> > aws-appsync > aws-appsync-auth-link > @aws-sdk/[email protected]: This package has moved to @smithy/util-hex-encoding
warning <app> > aws-appsync > @aws-crypto/sha256-universal > @aws-sdk/[email protected]: This package has moved to @smithy/hash-node
error Error: incorrect data check
    at Zlib.zlibOnError [as onerror] (node:zlib:189:17)
yarn install v1.22.21
info No lockfile found.
[1/4] Resolving packages...
[2/4] Fetching packages...
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.] running command [yarn --no-bin-links --production]
ShellCommandExecutionError: Received error [Error: Command failed with exit code 1: yarn --no-bin-links --production
warning <app> > aws-appsync > [email protected]: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
warning <app> > aws-appsync-auth-link > @aws-sdk/[email protected]: This package has moved to @smithy/util-hex-encoding
warning <app> > aws-appsync > aws-appsync-auth-link > @aws-sdk/[email protected]: This package has moved to @smithy/util-hex-encoding
warning <app> > aws-appsync > @aws-crypto/sha256-universal > @aws-sdk/[email protected]: This package has moved to @smithy/hash-node
error Error: incorrect data check
    at Zlib.zlibOnError [as onerror] (node:zlib:189:17)
yarn install v1.22.21
info No lockfile found.
[1/4] Resolving packages...
[2/4] Fetching packages...

Additional information

No response

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 @pr0g, thank you for reaching out. From the logs provided it appears this is occurring on the installation. Could you try changing directories into the amplify/backend/function/<function-name> and run yarn install do you observe similar errors?
if the installation does not throw an error and if you run amplify push at the root of the project does the error still occur?

[pr0g]

Hi @ykethan, thank you very much for getting back to me so quickly, I really appreciate it!

Thanks for the suggested approaches, I'm in UTC+0, so will try this tomorrow and leave an update here with how things go and update the state of the issue then.

Cheers!

[pr0g]

Hi @ykethan, this issue appears to have resolved itself.

I'm not 100% sure what actually fixed it 🤔 But I think quite a lot of our dependencies and Amplify CLI were out of date which may have been contributing.

I'll close the issue for now and report back if I see it happen again and can find a repro. Thanks!

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