Replies: 11 comments 1 reply
-
We are getting the same error, were you able to find the source of the problem? |
Beta Was this translation helpful? Give feedback.
-
@frottke We haven't done any further investigation, awaiting feedback from MS on how to manage / configure. |
Beta Was this translation helpful? Give feedback.
-
Judging from the error - did you try to use the Prerelease-compiler? |
Beta Was this translation helpful? Give feedback.
-
I'm not aware of an AL:GO setting for using the Prerelease-compiler? Couldn't find any proper guidelines on how to achieve this in the Usage Scenarios / Workshop / Settings documentation... |
Beta Was this translation helpful? Give feedback.
-
The problem here is the missing partner runtime package. |
Beta Was this translation helpful? Give feedback.
-
I'm not exactly sure what you mean with missing partner runtime packages. We have in our case no dependencies to other apps except the Microsoft Application. the error also appears when using localdevenv.ps1 (might be easier to debug? :) ) |
Beta Was this translation helpful? Give feedback.
-
Did this issue get resolved after the release of 25.0 ? |
Beta Was this translation helpful? Give feedback.
-
Still failing :( |
Beta Was this translation helpful? Give feedback.
-
Could you create a public repository, which reproes this problem? |
Beta Was this translation helpful? Give feedback.
-
We are also getting the same error with 24.0 (26.0 next major). I can provide a public repository, might be not today though. |
Beta Was this translation helpful? Give feedback.
-
More than 8 months later, this issue (converted to discussion without explicit justification?) is still Unanswered. Please provide an update, thank you. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Question
We have the following setup:
One repo, with multiple projects / apps, most having dependencies on each other (minimum against Core)
Core app has an additional dependency against a 3rd party app, which is included in the repo under Core project, .appSourceCopPackages folder.
Core app manifest file:
All actions run well / compile properly against BC24.
We would like to be informed about possible AppSource validation errors, by periodically running the 'Text Next Major' action on the main branch.
When running the 'Text Next Major' action for the entire repo, the action fails with errors:
logs_28540920193.zip
Side note: As mentioned on Yammer (https://www.yammer.com/dynamicsnavdev/#/threads/show?threadId=2959605473320960), our devs are focusing on the maintaining the main branch only (no plans to increase the application version to 25.0 within the next 5 months), how can they be alerted of these 25.0 validation errors upfront when working on a branch that has minimum dependency set to 24.0? (while avoiding the hassle of maintaining separate 'nextmajor' branches or uptaking preprocessorsymbols). Their reality is still 24.0.
...
we're not looking to implement the 'hotfix' process (https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-hotfixing-appsource-app) , as we won't release any Application 25.0 version soon.
Beta Was this translation helpful? Give feedback.
All reactions