Small and medium business | Business Central, N...

error AL1024: A package with publisher, name, and a version compatible could not be loaded

(8) Share

Report

Posted on by Jinesh K

112

Hello Everyone!

I am getting the following error in VS Code while trying to run an AL extension:

error AL1024: A package with publisher '{PartnerName}', name ' {AppName}', and a version compatible with '3.25.0.31' could not be loaded. Symbols for the requested app {AppName} by {PartnerName} {VersionNo.} could not be found among this tenant's installed apps. AppGroup Id 2450'. The original extensions have been restored.

Here is the scenario:

We have multiple extensions deployed in the same customer tenant.
Different teams work on different apps/extensions.
I usually work on App A.
For a particular task, I needed to use table from another extension, so I added it as a dependency in app.json.
I was able to successfully download the symbols without any issue.
However, the moment I try to run/publish the app from VS Code, I get the above error.

Additional details:

The dependent app is already installed in the target environment.
The installed version exactly matches the dependency version specified in app.json.
Symbol download succeeds, so the dependency appears to be discoverable initially.

Has anyone faced a similar issue where symbols download correctly, but publishing/running fails with AL1024?

Any suggestions on what could cause this mismatch during publish/runtime validation would be appreciated.

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (9)

Answers (0)

Sort by

Suggested answer

YUN ZHU 102,476 Super User 2026 Season 1 on at

Like
a
(4)

Report
Copy link

Link copied!

Hi, I recently encountered this issue. If you add dependencies using the method below, the standard will use the full version number. Changing the version number to only include "major" will solve the problem.

"version": "28.1.49838.50065" -> "version": "28.0.0.0"

Thanks

ZHU

Was this reply helpful? Yes No
Suggested answer

Pallavi Phade 5,742 Super User 2026 Season 1 on at

Like
a
(2)

Report
Copy link

Link copied!

Namaste @Jinesh K

I agree with ZHU . Please do the needful . We also add entire version in app dependancies and then download symbols .

We check from Extension screen in front end .

Warm Regards

Pallavi Phade

www.linkedin.com/in/pallaviphade131116

Was this reply helpful? Yes No
Suggested answer

OussamaSabbouh 18,383 Super User 2026 Season 1 on at

Like
a
(3)

Report
Copy link

Link copied!

Hello,

This usually means the dependency identity used at publish time is not matching what the server can load, even if symbols downloaded successfully. First check the dependency in app.json very carefully: publisher, name, id, and version must match the installed app exactly — also watch for a hidden/leading space in the name, because your error shows name ' {AppName}', which can break matching. Then delete .alpackages, run AL: Clear Cache, download symbols again, rebuild, and publish. Also confirm you are publishing to the same tenant/environment where the dependency is installed, and that all indirect dependencies of that dependent app are installed too. If it still fails, ask the other team to provide the exact .app package or app manifest used in that environment, because the symbol package you downloaded may not represent the same app identity the runtime validates during publish.

Regards,
Oussama Sabbouh

Was this reply helpful? Yes No
Jinesh K 112 on at

Like
a
(2)

Report
Copy link

Link copied!

Thanks for the replies,

I Tried the above method mentioned by Yun Zhu and also tried using only the major version, but none of it worked. in both the case I got the exact same error.

Do I need to change something in the app that my app is dependent on?

Was this reply helpful? Yes No
LY-08060831-0 4 on at

Like
a
(2)

Report
Copy link

Link copied!

Hi Jinesh,

Not sure if you're still running into this issue but I was getting the same thing and I could not figure it out.

Turns out the issue was because both my extensions were dependent on each other. I had recently added a dependency for extension B into my app.json file for my main extension A. Downloading symbols was fine but deploying kept on running into the same error as you. After removing the dependency for extension B in my app.json for my main extension A and moving the code I needed from extension B into A, I had no problems deploying.

Hope this helps.

Was this reply helpful? Yes No
Suggested answer

Kamal Khakhkhar 3,570 on at

Like
a
(2)

Report
Copy link

Link copied!

hii there ,
Great to here issue is solved , for this as per requirement Application can not be inter-dependent in business central , with you found. please mark this verified to everyone knows this is solved.

Thank You .

Kamal Khakhkhar

Was this reply helpful? Yes No
Suggested answer

Grigorios Mavrogeorgis 2,801 Super User 2026 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi,

the giveaway here is the AppGroup Id in the message. When the dependency lives in an app group, publishing from VS Code has to bring the whole group along, and the runtime validation checks the group as a unit, not just your single dependency. Symbol download is a different step, that one only needs the package to read the table, so it succeeds and makes you think all is fine, then publish does the stricter group check and fails.
So even though the installed version matches exactly, BC is not finding a compatible set for that whole AppGroup at publish time, usually because another app in the group, or the dependency itself, is at a version the tenant does not have in a loadable state. I would check the dependency app and anything grouped with it are all actually published and not just installed, and that the versions across the group line up, not only the one you put in app.json.

Are you publishing straight to the customer tenant or to a sandbox copy? And is the other team's app a per-tenant extension or AppSource? That changes how the group resolves.

Glad to help - follow up if anything is unclear.
► If this solved it, marking it verified helps others too.
Regards,
Grigorios Mavrogeorgis
Business Central Consultant & AL Developer
Work: Gmsoft Limited
Blog: insidebusinesscentral
LinkedIn: linkedin.com/in/gregorymavrogeorgis

Was this reply helpful? Yes No
CU21061052-0 4 on at

Like
a
(0)

Report
Copy link

Link copied!

I ran into a similar AL1024 issue before. In my case, the root cause was a circular dependency between extensions. Symbol download worked fine, but publishing failed because App A depended on App B while App B also had a dependency chain back to App A. It may be worth checking whether any inter-dependencies exist between your extensions, as Business Central does not support circular app dependencies.

Managing dependencies properly is important in many development environments, including Roblox tools such as Delta Executor, where a clean and well-organized setup helps ensure smooth loading and better overall performance.

dltaexecutor

Was this reply helpful? Yes No
Suggested answer

Khushbu Rajvi. 23,132 Super User 2026 Season 1 on at

Like
a
(2)

Report
Copy link

Link copied!

Please check for a circular dependency between the extensions. It can cause publish-time dependency resolution issues even when symbol download succeeds. However, AL1024 can also be caused by an app identity, version, tenant, or AppGroup mismatch. Verify the full dependency chain and the installed app versions before concluding that the issue is circular dependency related.

Was this reply helpful? Yes No