Production App, dependency error

Hi, I’m fairly new to business central development, but I’ve upladed 20 apps or so but today ran into a problem. It’s giving me the following error, I’ve checked the app ID, Name, publisher, & version on all 3 dependencies and everything looks okay. No other extensions are dependent on my app, what might I be doing wrong?

Deployment failed. Errors: App ID : 21aa1f2e-4271-4dfa-8aea-035c3fffc92b Message : { The app (or one of its dependencies) does not have a version that is compatible with other installed apps on the tenant. } - Job Id : 190df832-5a81-4031-bb38-872435a62b24

Hi @Nick_Firth,

From my own experience, as the error says, you have a dependency problem.

Carefully check that all dependency apps are installed and that the version is correct for all of them. In the past I had these types of errors and the problem was the version of one of the installed dependency app (the application needed a newer dependency app).

Hi, thank you for replying, I double checked and I still don’t see any difference. I’m using an previously installed app installed to production. I wish MS would tell you what the missing dependency or version is. I’ve uploaded this to the sandbox 10 times with no issue. The App ID, name, publisher are the same, just amending the version. the code is below and the versions from installed extension are the following:

[
Barcode Generator](javascript::wink: Insight Works v. 1.4.8487.1
|My Customizations1|||—|—||Item Inc.|v. 1.0.0.62|
[ITMI Custom](javascript::wink: JourneyTEAM v. 21.0.0.22

{
“id”: “21aa1f2e-4271-4dfa-8aea-035c3fffc92b”,
“name”: “Item Inc Customizations”,
“publisher”: “Nick Firth”,
“version”: “1.0.0.41”,
“brief”: “”,
“description”: “”,
“privacyStatement”: “”,
“EULA”: “”,
“help”: “”,
“url”: “”,
“logo”: “”,
“screenshots”: ,
“platform”: “1.0.0.0”,
“application”: “22.0.0.0”,

“dependencies”: [
{
“id”: “62080fe0-d57f-4d4c-aed1-ac539db3a244”,
“name”: “Barcode Generator”,
“publisher”: “Insight Works”,
“version”: “1.4.8487.1”
},
{
“id”: “30f66ad9-e0c9-4143-a532-eafd2bd8511b”,
“name”: “My Customizations1”,
“version”: “1.0.0.62”,
“publisher”: “Item Inc.”
},
{
“id”: “05d8534c-b7cb-43ce-a6ed-74d8fdbd0e96”,
“name”: “ITMI Custom”,
“version”: “21.0.0.22”,
“publisher”: “JourneyTEAM”
}
],
“idRanges”: [
{
“from”: 50150,
“to”: 50199
}
],
“resourceExposurePolicy”: {
“allowDebugging”: true,
“allowDownloadingSource”: true,
“includeSourceInSymbolFile”: true
},
“runtime”: “11.0”,
“features”: [
“NoImplicitWith”
]
}

At first glance everything seems fine.

In the past we had another problem, the version that you put in the dependencies part of app.json is the minimum version that your application needs to work correctly, but when we develop the application, we work in a Sandbox or Docker, and sometimes the version that we actually use is greater than the version we have in the dependencies part, and if we use some new function or object that was not present in the version we have in the dependencies part… this ends up with a compatibility error, because it is using functionality that is not present in the installed version of the dependency application.

You say that in Sandbox you have no problem installing and using your extension… do the dependent applications have the same version as in the production environment?

Good morning, I figured it out, it was a conflict with another extenstion. I had added a field to a report on another extension and then created a brand new report in another extension utilizing the field from the other and looks like I had named the report differently. Thank you so much for you help, every suggestion always gets you thinking of new possibilities.

1 Like