Cannot start new build due to inconsistent dependencies involving producer LSG_ODC_Components_Library: The dependencies graph is not valid: one of the producers can be found with a different version. Please address the situation before republishing. (OS-BLD-BLD-40004)
An error has occurred while building the application: Error while Requesting Build (OS-DPL-50205)
In ODC, if Library 1 is a consumer for library 2, then library 2 cannot become the consumer for library 1. hence the issue. just manage it n issue gets resolved.
either remove the library being consumed n you will resolve the issue
try to remove unused dependencies or if you have graph component check the version or test it after removing it.
Hi @yashas chikkakalya lingaiah ,
In service studio, go to module tab
1. Click manage dependencies (ctrl + Q).
2. Look for LSG_ODC_Components_Library and check if there are multiple versions.
3. Select the latest version and refresh dependencies, and publish. (or)
1. Click Remove unused dependencies (ctrl+shift+D).
2. Check for broken dependencies, fix any dependency conflicts and re-publish.
Thanks,
Dhanasingh Dennison.
Hi @yashas chikkakalya lingaiah
The error message you're encountering indicates that there is an issue with inconsistent dependencies in your OutSystems application, particularly involving the LSG_ODC_Components_Library producer. This can happen if there are different versions of the same dependency or component in your application, which are causing conflicts.
To remove the error Check the version being referenced and make sure that all modules use the same version of this library. If necessary, update the dependencies to point to the latest version. In the dependency list, locate LSG_ODC_Components_Library and update it to the correct version. Regards ,
Rajat
@yashas chikkakalya lingaiah ,
1° I think, from the error message you share and from the name of your library, that you are experiencing problems on ODC. Please tag this question correctly, not Reactive, but ODC, because now you get all kinds of answers that relate to O11, not ODC.
2° I don't know how to fix this particular error, or how it is caused, but Library versions in an ODC application are not a simple thing. Probably, you want all your producers to be on the same version of any possible common other producers to avoid this kind of problem.
3° See this article I wrote last weekend, it is not about this error, but it talks about the complexities of library versioning.
Dorine