The action is completed successfully, even when there is an error

[samuelcecilio]

Apparently the error code that happens inside the entrypoint is not forwarded to github, so this action always returns success.

This results in a false positive, because to know that something is wrong, I need to go to the workflow and click on the step that is marked as success, but at the end of the log there is an error.

https://docs.github.com/en/actions/creating-actions/setting-exit-codes-for-actions#setting-a-failure-exit-code-in-a-docker-container-action

[moweb-Vaidehi]

Same issue happening with me

[amorujao]

In my case I was still setting up the project and had an error in the inputs (empty appId) and it also succeeded despite showing an error message in the logs.

[arthurljones]

This just happened to my team - we changed a build config and that unexpectedly changed the output file.

Another action in the script posts a comment on the PR when the build is ready, which still fired, because the upload action reported success despite an error.

[emartynov]

I assumed it should fail the job. Apparently, it doesn't. Can we fix it?

[JulienDupontDev]

Same here, got "Error: failed to determine AAB info. HTTP Error: 403, Firebase App Distribution API has not been used in project" but job still shows as successful, not very good for CI / CD to not have reports about a failed deployment xD