Skip to content

[Bug]: Error: No artifacts found for this project #1532

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
mcebailly opened this issue Mar 24, 2025 · 11 comments
Closed

[Bug]: Error: No artifacts found for this project #1532

mcebailly opened this issue Mar 24, 2025 · 11 comments
Assignees
Labels
bug Something isn't working Cannot repro Unable to reproduce

Comments

@mcebailly
Copy link

AL-Go version

6.4

Describe the issue

I have recently ran Update AL Go Settings to version 6.4 on a project in the App Store.

In the past I have ran the Create Release feature and uploaded the .app file which was signed.

When I run Create Release now I get this error:

Error: No artifacts found for this project
Error: Process completed with exit code 1.

Expected behavior

A .app file is created from the Create Release

Steps to reproduce

Run the Create Release Action

Additional context (logs, screenshots, etc.)

logs_36141548334.zip

Here are the logs of the run

@mcebailly mcebailly added the bug Something isn't working label Mar 24, 2025
@freddydk
Copy link
Contributor

The way Create Release works is that it promotes a build to a release - it doesn't build the app again.

When you say that earlier, you created a release and uploaded the binaries yourself - it sounds like you didn't use CI/CD workflow to create a build, which you then released - or?

@mcebailly
Copy link
Author

mcebailly commented Mar 25, 2025 via email

@freddydk
Copy link
Contributor

Please use the GitHub UI instead of replying to the emails - it becomes confusing.
I would need the log from the failing CI/CD to see why that failed

@mcebailly
Copy link
Author

The build itself was skipped, the error I showed there shows at the main Action page of the CI/CD under Annotations. Is there a specific log I can send? I've attached the initialization if that helps

logs_36137804915.zip

@freddydk
Copy link
Contributor

Does it say anything about why it skips the build?

@freddydk
Copy link
Contributor

You can try to run the troubleshoot workflow - maybe you have a secret with an illegal value causing failures down the line

@freddydk freddydk self-assigned this Mar 28, 2025
@mcebailly
Copy link
Author

I've narrowed this down to a JSON rendering issue in the build.

This is the error:

Error when evaluating 'if' for job 'Build'. .github/workflows/CICD.yaml (Line: 175, Col: 9): could not get operand for index access: could not get operand for index access: Error from function 'fromJson': empty input

On that line:

if: (!failure()) && (!cancelled()) && fromJson(needs.Initialization.outputs.buildOrderJson)[0].projectsCount > 0

So my assumption is that buildOrderJson is empty

@mcebailly
Copy link
Author

Attached is the CICD log. I did update to v7 of the libraries. It looks like in the DetermineProjectsToBuild step it does find my app and it comes back with JSON in the step.

logs_36800200139.zip

@freddydk
Copy link
Contributor

freddydk commented Apr 7, 2025

It looks like you have a secret, which contains a multi-line json construct.
Looking at the log, github thinks that the } character is a secret and will not transfer anything between jobs where this is the case.
The troubleshoot workflow should tell you which secret is the problem.

@freddydk
Copy link
Contributor

Did you locate the problematic secret?

@freddydk freddydk added the Cannot repro Unable to reproduce label Apr 14, 2025
@mcebailly
Copy link
Author

Yep! This was the Azure Credentials secret. It had line feeds in it and by removing them we were able to build. Thank you for following up sir!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Cannot repro Unable to reproduce
Projects
None yet
Development

No branches or pull requests

2 participants