Alex Ilies

Stuck on this issue, too

@ykethan any updates on this issue? Don't know how you prioritised it, but it's kind of a blocker, since if updating to version >=10.0.0 there is no any workaround to...

@ykethan thank you for your fast response. Just removing the `--simple` flag is not a solution. By removing the flag, a new environment is created at every commit. Indeed, the...

Closing this issue, as the fix was done in #11179 and released with Amplify v10.3.2. Good job!

Unfortunately, I have to re-open it. After more testing, the hooks are still running only once - at the first build.  More findings. How to reproduce the issue: **1...

@evcodes this is a good news. I run on 9.2.1

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

Same issue. Will be helpful to have some updates here.

I'm strongly assume that this issue appears just on remote CI/CD, and the reason is that you use the amplifyPush script: https://github.com/aws-amplify/amplify-hosting/blob/main/scripts/amplifyPush.sh The workaround: use amplifyPush --simple flag For the...

Don't know your context, but I solved the issue by providing this congifs in project.json: ``` "configurations": { "production": { "tsConfig": "libs/shared/angular-components/tsconfig.lib.prod.json" }, "development": { "tsConfig": "libs/shared/angular-components/tsconfig.lib.json" } }, ```