Skip to content

[Bug]: Publish App Error on Pull Request Build with dependency on Continia Expenses #1512

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

Open
nickgoddard777 opened this issue Mar 17, 2025 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@nickgoddard777
Copy link

AL-Go version

preview

Describe the issue

I have just created a PR for some functionality that is depedant on Contina Expenses. I can see in the logs that the script has worked out all the Continia dependencies, published them to my self-hosted docker container, compiled my app but when it tries to publish my app to the docker container I get errors saying it can't find various Continia obects I am referencing.
In the logs when I look at the last Intalled Apps entries I can see all the Continia Apps are installed.
Over the weekend I have also just moved us over to the PReview build and implemented Incremental Builds as this project has several apps and test apps.

Expected behavior

I would expect the app to be published

Steps to reproduce

  1. Create an App with a dependency to Continia Expenses
  2. Setup the app to use Incremental Builds from the AL-GO Preview
  3. Add a permissionSet Extension which extends CEM-APPROVE
  4. Commit the App and create a PR.

Additional context (logs, screenshots, etc.)

2_Build Infopro Haynes (Default) _ Infopro Haynes (Default).txt

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

freddydk commented Mar 18, 2025

The nuGet packages you get from the AppSource feed are only symbols - they are not runtime packages, and as such they cannot be used to deploy apps to a container.
You can use them to build the app, but not to deploy and test.
We should fine a better error message for this.
We are also working on finalizing NuGet support to better allow partners to share NuGet runtime packages with partners and also allow you to deploy and run tests on online environments if you cannot get the runtime package.

@freddydk freddydk self-assigned this Apr 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants