I have developed a solution in Pega Studio 19.1 and I am able to generate the package successfully via the deploy option. Each time I use the deploy option, I do see the version incrementing which is reflected in the manifest. However, when we try to load the latest package into Runtime on another machine via the local project option, the latest version is not loaded. Instead, an older version of the package is being loaded - I know this because my latest changes in RDA Solution are not there when automation is triggered. What could be the issue? We end up restarting the machine and removing/renaming package files to "somehow" load the latest version - but this does not seem to always work.
Any input would be greatly appreciated.
When you create the deployment package, are you copying both the .manifest and .openspan files out to the deployment package location? I would check the RuntimeLog to see what might be happening. I have seen where Runtime doesn't like to load older packages than the current one, but that may have been an old issue and one I have not encountered recently. In addition, I would check the extract directory (which is usually %LocalAppData%\Pegasystems\19.1\Projects). Perhaps when you terminate your prior Runtime, it is still leaving something open that is preventing the extract directory from getting overwritten with the new package. Try reproducing the issue, and when you see the old package loading, shut down Runtime and attempt to clear the contents of the extract directory. If you are unsuccessful, it will likely tell you that it can't delete because files are in-use. If that is the case, you'll just need to make sure you are closing everything when you shut down Runtime.