Patch Org Creation Failing with Error "A newer version of this package is currently installed"
AppExchange , Packaging , Partner
Last updated 2022-02-10 ·Reference W-2323058 ·Reported By 3 users
Summary
Given a child package with a dependency tree of multiple parent packages that, themselves, reference a common parent package (for example, common package 'util').
If the parent packages were uploaded for different versions of the common util package then when an attempt is made to create a patch org for the child package it can fail.
Repro
In order to make a child package have a parent package you can install the parent package in the child DE org. Then add a custom field to a custom object that came from the parent package. Then add "Custom Field" (not "Custom Object") to your child package.
util v1.2 util v1.0 util v1.1
| | |
| ParentA Package ParentB Package
| | |
-------------------------------------------------------------
|
Child Package
To reproduce, create a package hierarchy like the one pictured above. Grant access to all users when installing packages.
Workaround
* The partner/ISV must upgrade all parent package DE orgs in the package dependency tree to a common "latest" version of whatever util package all of the packages extend
** to do this, install a new util package in all of your DE orgs in your tree
* Then upload a new version of all of your parent packages
* Then upgrade the parent packages in your child package
* Now the partner/ISV can create a patch org for the child package
Reported By (3)
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.