Marketplace AL Language extension cannot publish to BC 29 sandbox: server requires Debugger 9.0, latest release/pre-release support only up to 8.0
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 8/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- vscode
- Ambito
- developer-experience
Direzione di ricerca
The failure is the version-compatibility check that rejects the Marketplace AL extension when the server reports Debugger 9.0; the supported-debugger list is what needs to change, and the attached publish-error-output.txt and launch.json show the failing requests. Resolving it means a maintainer publishing a release that supports debugger 9.0, not a code edit a newcomer can finish alone. Done means the Marketplace build connects to a BC 29 sandbox with Download Symbols, Publish and Debug all succeeding.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Summary
After our BC SaaS sandbox was updated to BC 29, the AL Language extension from
the VS Code Marketplace can no longer connect to it. Download Symbols, Publish
(Ctrl+F5) and Debug (F5) all fail immediately with:
Error: This AL extension version for Visual Studio Code cannot be used with
the specified server. Please update the AL extension from the Visual Studio
Code marketplace.
There is no newer version on the Marketplace to update to.
Environment
- Business Central: IN Business Central 29.0 (Platform 29.0.55857.0 + Application 29.0.54011.55935)
- Environment type: SaaS Sandbox
- Server reports: Runtime 18.0, Web API 7.0, Debugger 9.0
- VS Code 1.141.0, Windows 11 (10.0.26200)
- app.json: "application": "29.0.0.0", "runtime": "18.0"
Results per AL extension version
| AL version | Source | Supported debuggers | Result |
|---|---|---|---|
| 18.0.2819426 | Marketplace, latest release (2026-10-01) | up to 8.0 | Blocked: "cannot be used with the server" |
| 30.0.2813176 | Marketplace, latest pre-release (2026-10-01) | up to 8.0 | Blocked: "cannot be used with the server" |
| 18.1.2825563 | BC artifact sandbox/29.0.54011.55935/platform (same build as our sandbox) | up to 7.0 | Blocked: "cannot be used with the server" |
| 18.1.2842859 | BC artifact sandbox/29.0.54011.56119/platform | up to 9.0 | Publish works (debugging fails, reported separately) |
Steps to reproduce
- Install the latest AL Language extension from the Marketplace
(18.0.2819426, or pre-release 30.0.2813176). - Open a project targeting application 29.0.0.0 / runtime 18.0.
- Run AL: Download Symbols, Ctrl+F5 or F5 against the BC 29 sandbox.
- The request to /v2.0//dev/metadata?tenant= returns
the version-incompatibility error. Supported runtimes and Web API match the
server, but debugger 9.0 is missing from "Supported debuggers".
Observations
- Runtime (18.0) and Web API (7.0) are supported by all versions tested; only
the debugger version (9.0) blocks the connection. - The AL VSIX shipped in the sandbox's own artifact (29.0.54011.55935) supports
only debuggers up to 7.0, so the server's debugger endpoint appears to have
been updated ahead of the AL tooling released with that build. - The only working build we found, 18.1.2842859, is not available on the
Marketplace. We had to extract it manually from the BC artifact CDN.
Workaround in use
Manually installed ALLanguage.vsix 18.1.2842859 extracted from
https://bcartifacts-exdbf9fwegejdqak.b02.azurefd.net/sandbox/29.0.54011.56119/platform
(path inside: ModernDev/PFiles/Microsoft Dynamics NAV/290/AL Development Environment/ALLanguage.vsix).
Auto-update for the AL extension has to be disabled, otherwise VS Code
replaces it with the incompatible Marketplace build.
Expected
A Marketplace release (or pre-release) of the AL Language extension that
supports debugger protocol 9.0 should be available when sandboxes are
updated to it.
Request
Please publish an AL Language extension version supporting debugger 9.0 to
the Marketplace, or confirm the recommended version for BC 29 Platform 29.0.55857.0.
- Lingua principale
- PowerShell
- Stelle
- 884
- Fork
- 285
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di microsoft/AL
-
accepted al-tools bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
-
accepted
Difficoltà 5/5 Più di una settimana Idoneità per principianti 12/100
-
suggestion
Difficoltà 4/5 3-5 giorni Idoneità per principianti 45/100
-
accepted
Difficoltà 4/5 3-5 giorni Idoneità per principianti 45/100
-
accepted
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
Tutte le issue di microsoft/AL
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
NationalSecurityAgency/ghidra#9883 ·
I maintainer di solito rispondono entro 2 giorni
-
Add pre-commit with lintingApertagood first issue No-AI
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
-
Frontmatter next to `src:` is applied to every imported slide, not only the first (undocumented)Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
I maintainer di solito rispondono entro 1 giorno
-
bug needs-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
Fission-AI/OpenSpec#2084 ·
I maintainer di solito rispondono entro 2 giorni
-
[scanner] check:spelling skips blog/ — posts and author metadata are never spell-checkedForse già presa @hivecommons-hive l’ha presa oggi. Apertaagent/scanner bug hive/covered-by-pr hive/hosted-available-lke648397-260827-5n31
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 72/100
cncf/endusers#1452 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno