Good morning,
At my company, we have some web-based applications that are linked to a mobile library for API calls, etc. The problem is that, since the library is mobile-based, if we make any changes, we can't update our apps (it won't let us and doesn't detect it, because I understand that it's web-based). We have tried everything, but it won't update (managing dependencies, adding public elements, deleting dependencies, and re-importing it...). Do you know if there is any way to do/force this update?
Thank you!
Hello @Amin El Meziani,
Be aware that there are two steps: one is the publish and the other is the release. The publish you already did in ODC Studio, but there is still a release button in the ODC Portal so that you can make it visible for apps or other libraries.
After that, it should be usable for both mobile and web apps. You should see a pop-up in the app saying “Review Updates” once you open the app or library in ODC Studio that is using it.
You can double-check if it is released.
You can also release it in ODC Studio, like in the second screenshot.
Refer to this documentation: Libraries
Whenever publishing the library, it forces all the consumers to update to new version. In this case, there are changes in the BPFramework that makes IloguerplacesaparcamentCLONE not compatible anymore (UI, input parameters, output parameters, etc), need to open the IloguerplacesaparcamentCLONE to refresh it manually before publish the library.
In ODC, its different from O11, the library can be changed many times, but we have the function to let it public to all other apps.
Please refer this link for more information: https://success.outsystems.com/documentation/outsystems_developer_cloud/building_apps/libraries/#release-library
Hello,
Thank you both for your help. I clicked the “Release library” button, but when I update my web application, it shows me this warning:
When I publish, I get this error:
IloguerplacesaparcamentCLONE is still using an older version of the BPFramework library. I think it should be updated as well (meaning review the updates), and the changes introduced in the newer BPFramework version should be reviewed.
Hi everyone,
Thank you very much for your help. I followed all your instructions and was finally able to publish the application. What we did was create a separate library where we copied only the blocks we needed. This way, we deleted the obsolete library that was causing errors or was corrupted, and when we re-imported the blocks, we were able to publish without any problems. With this alternative solution, we can now move forward with our testing.
Once again, thank you very much for your support.
Amin
You’re welcome anytime.
great to hear that you can solve the blocker