Skip to content
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

Downloading wrong Symbol Versions from Cloud instances #7984

Open
IDAG-FHO opened this issue Feb 24, 2025 · 14 comments
Open

Downloading wrong Symbol Versions from Cloud instances #7984

IDAG-FHO opened this issue Feb 24, 2025 · 14 comments

Comments

@IDAG-FHO
Copy link

IDAG-FHO commented Feb 24, 2025

Downloading the symbols from Cloud tries to download the Microsoft App Version 25.4 although we have installed the version 25.3. This happened today, Monday 24.02.2025 on all our projects that are in cloud and without any code/settings change from our side.

To reproduce:

  • If you have an app that you can publish in a cloud instance with the actual version, delete the symbol references in your ".alpackages" folder. Try to download the symbols.
  • Create a new Project "AL GO!". Configure your launch.json to a cloud instance with the Microsoft App Version 25.3. Try to download the Symbols.

Result:
[2025-02-24 16:26:38.65] The request for path /v2.0/BCTEST/dev/packages?publisher=Microsoft&appName=Business%20Foundation&versionText=25.4.0.0&appId=f3552374-a1f2-4356-848e-196002525837&tenant=d958dac5-4f95-4943-96ed-1ada1fc0581e failed with code NotFound. Reason: No published package matches the provided arguments. [2025-02-24 16:26:38.65] The request for path /v2.0/BCTEST/dev/packages?publisher=Microsoft&appName=System%20Application&versionText=25.4.0.0&appId=63ca2fa4-4f03-4f2b-a480-172fef340d3f&tenant=d958dac5-4f95-4943-96ed-1ada1fc0581e failed with code NotFound. Reason: No published package matches the provided arguments. [2025-02-24 16:26:38.70] The request for path /v2.0/TEST/dev/packages?publisher=Microsoft&appName=Base%20Application&versionText=25.4.0.0&appId=437dbf0e-84ff-417a-965d-ed2bb9650972&tenant=d958dac5-4f95-4943-96ed-1ada1fc0581e failed with code NotFound. Reason: No published package matches the provided arguments. [2025-02-24 16:26:38.70] Error: Failed to download the following references: System Application by Microsoft (25.4.0.0) Business Foundation by Microsoft (25.4.0.0) Base Application by Microsoft (25.4.0.0) [2025-02-24 16:26:38.70] All reference symbols have been downloaded.

@danexoag
Copy link

danexoag commented Feb 25, 2025

I have the same problem since yesterday, Feb 24. With all existing projects a Donwload symbol leads to the error message that the reference to 25.4.0.0 cannot be downloaded.
Installed AL Language extension is 14.2.1249978
The sandbox has version 25.3.28755.30175.
"application" ist set to 24.0.0.0
"runtime" is set to "14.0"
[2025-02-25 08:11:06.59] Error: Failed to download the following references: System Application by Microsoft (25.4.0.0)
Business Foundation by Microsoft (25.4.0.0)
The error can be reproduced by creating a new project with AL: Go! and then downloading the symbols.
Environment shows Version 25.3.28755.30175 with no further updates available.
Localisation: Swiss CH

It even happens with a blank new AL:Go! Project. So pure Microsoft.

@Aize-S
Copy link

Aize-S commented Feb 25, 2025

Same issue in here. Localisation NL.

@evenmiles
Copy link

I have same issue in localisation ES. I've tried to "force" the base application version in dependencies without success.

@Aize-S
Copy link

Aize-S commented Feb 25, 2025

Updated to BC25.4, now it works again.

@IDAG-FHO
Copy link
Author

Updated to BC25.4, now it works again.

Yes, now that wen can install the 25.4 update that is one way.
But I expect that problem to happen on the next versions, too. And I hope that we get a fix for that. Or at least a hint what we can do about it.

@Aize-S
Copy link

Aize-S commented Feb 25, 2025

Updated to BC25.4, now it works again.

Yes, now that wen can install the 25.4 update that is one way. But I expect that problem to happen on the next versions, too. And I hope that we get a fix for that. Or at least a hint what we can do about it.

I agree that it's not something that we would like to have happen in next versions.

@hreinnbasicform
Copy link

What version is your app running?

From what I can tell, if an app depends on another app with a version higher than the platform version, it attempts to load the latest symbols platform version.

I’m running into an issue with an app with version 24.0.x.x.
It depends on another app with version 23.11.x.x, in my app.json but the only version of that dependent app installed in the SaaS environment is 25.12.x.x.

When downloading symbols in the development environment, it seems to try fetching the latest symbol version (25.4.0.0), even though the SaaS environment is running 25.3.x.x.

@AnasNavTech
Copy link

Not able to download the symbol today onwards, Any solution

error AL1022: A package with publisher 'Microsoft', name 'Business Foundation', and a version compatible with '25.4.0.0' could not be found in the package cache folders: d:\RS.alpackages
error AL1022: A package with publisher 'Microsoft', name 'System Application', and a version compatible with '25.4.0.0' could not be found in the package cache folders: d:\RS.alpackages
error AL1022: A package with publisher 'Microsoft', name 'Base Application', and a version compatible with '25.4.0.0' could not be found in the package cache folders: d:\RS.alpackages

@IDAG-FHO
Copy link
Author

Only solution I can provide at the moment is to update a sandbox environment to BC Version 25.4 and develop with the symbols downloaded from there. Deployment will still work on 25.3.

@AnasNavTech
Copy link

after updating getting error in object like below

Image

@hreinnbasicform
Copy link

Restart extensionhost fixed the missing symbol for me, i.e. restart VSCode.

@hreinnbasicform
Copy link

Is any of the dependencies with a version higher than valid, i.e. 23.20.x.x - this seems causes the debug server to deliver the incorrect symbol files.

@AnasNavTech
Copy link

Thank you so much for swift reply . It works after reloading windows

@leelane0
Copy link

We have the same issue in localization FR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants