AL-Go icon indicating copy to clipboard operation
AL-Go copied to clipboard

[Question]: Error when running Test Next Major action

Open fvet opened this issue 1 year ago • 6 comments

Question

We have the following setup:

One repo, with multiple projects / apps, most having dependencies on each other (minimum against Core)

image

Core app has an additional dependency against a 3rd party app, which is included in the repo under Core project, .appSourceCopPackages folder.

image

Core app manifest file:

{
  "id": "c1fa90da-fc3f-4720-abd8-1b30fe8f3faf",         
  "name": "ESC Core",
  "publisher": "ESC bvba",
  "version": "24.0.0.0",
  "brief": "ESC Core Module",
  "description": "ESC Core module",
  "privacyStatement": "https://www.esc.be/en/privacy-policy",
  "EULA": "https://www.esc.be/en/terms-and-conditions",
  "help": "https://esc.be/support/",
  "url": "http://www.esc.be",
  "logo": "ESC.png",
  "screenshots": [],
  "platform": "24.0.0.0", // <<<
  "application": "24.0.0.0",  // <<<
  "idRanges": [
    {
      "from": 71791569,
      "to": 71791574
    }
  ],  
  "dependencies": [
    {
      "id": "dbe4cf4c-5910-4ad1-beee-394010c59802",
      "name": "Dynavision Core",
      "publisher": "Dynavision",
      "version": "23.0.14.0"
    }
  ],
  "contextSensitiveHelpUrl": "https://esc.be/",
  "runtime": "13.0",  // <<<
  "target": "Cloud",

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:

Error: AL1153 The referenced module 'System by Microsoft (25.0.24293.0)' with runtime reference version '14.0' cannot be loaded by the compiler with version '13.0'.
Error: AL1153 The referenced module 'System Application by Microsoft (25.0.23364.24332)' with runtime reference version '14.0' cannot be loaded by the compiler with version '13.0'.
Error: AL1153 The referenced module 'Business Foundation by Microsoft (25.0.23364.24332)' with runtime reference version '14.0' cannot be loaded by the compiler with version '13.0'.
Error: AL1153 The referenced module 'Base Application by Microsoft (25.0.23364.24332)' with runtime reference version '14.0' cannot be loaded by the compiler with version '13.0'.
Error: AL1153 The referenced module 'Application by Microsoft (25.0.23364.24332)' with runtime reference version '14.0' cannot be loaded by the compiler with version '13.0'.

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.

fvet avatar Sep 19 '24 12:09 fvet

We are getting the same error, were you able to find the source of the problem?

frottke avatar Sep 24 '24 07:09 frottke

@frottke We haven't done any further investigation, awaiting feedback from MS on how to manage / configure.

fvet avatar Sep 24 '24 07:09 fvet

Judging from the error - did you try to use the Prerelease-compiler?

waldo1001 avatar Sep 26 '24 09:09 waldo1001

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

fvet avatar Sep 26 '24 09:09 fvet

The problem here is the missing partner runtime package. When running Test Next Major - it automatically uses the compiler from the Next Major artifacts. I will do some investigations and get back in a few days

freddydk avatar Sep 26 '24 13:09 freddydk

The problem here is the missing partner runtime package. When running Test Next Major - it automatically uses the compiler from the Next Major artifacts. I will do some investigations and get back in a few days

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? :) )

frottke avatar Sep 26 '24 13:09 frottke

Did this issue get resolved after the release of 25.0 ? Does Test Next Major work with v26 now?

freddydk avatar Oct 17 '24 07:10 freddydk

Still failing :(

logs_29733413758.zip

fvet avatar Oct 17 '24 08:10 fvet

Could you create a public repository, which reproes this problem? My bingmaps repo: https://github.com/microsoft/bcsamples-bingmaps.pte - works fine with nextmajor (although it fails some tests - but building works)

freddydk avatar Oct 17 '24 09:10 freddydk

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.

frottke avatar Oct 21 '24 13:10 frottke