You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
App Id
dkn95cusc5c8
Region
us-west-2
Amplify Hosting feature
Backend builds
Describe the bug
We have a post-push.js script which runs on after every build. This has been working without fail for months. On Tuesday it stopped working for us on some of our existing branches. Today I created a new branch and post-push.js ran on it, but when redeploying post-push.js no longer runs. The post-push.js file exists in the app S3 bucket. When I pull the environment locally the post-push.js file exists. When I attempt to deploy locally it runs post-push.js locally.
Expected behavior
post-push.js should continue running after a build.
Reproduction steps
Add post-push.js to your hooks folder
Push to your github branch that is connected to amplify
It's due to the fact that the Amplify v10.0.0 changes how the Hooks are handled. Now you have to check-in them in the version control. The hooks folder isn't uploaded to S3 anymore.
I think, setting the version in the Amplify Console/You App/Build Settings/ to the previous version of Amplify: 9.2.1, will work for you.
Before opening, please confirm:
App Id
dkn95cusc5c8
Region
us-west-2
Amplify Hosting feature
Backend builds
Describe the bug
We have a post-push.js script which runs on after every build. This has been working without fail for months. On Tuesday it stopped working for us on some of our existing branches. Today I created a new branch and post-push.js ran on it, but when redeploying post-push.js no longer runs. The post-push.js file exists in the app S3 bucket. When I pull the environment locally the post-push.js file exists. When I attempt to deploy locally it runs post-push.js locally.
Expected behavior
post-push.js should continue running after a build.
Reproduction steps
Build Settings
Additional information
No response
The text was updated successfully, but these errors were encountered: