Salesforce Stack Exchange is a question and answer site for Salesforce administrators, implementation experts, developers and anybody in-between. It only takes a minute to sign up.
Sign up to join this community
When developing a managed (namespaced) package in a scratch org we'd also like to install another package to help fully test it's behaviour.
This other package actually requires the one in development and at present it's installation is failing since it thinks its dependency (the package in dev in the scratch org) isn't installed.
I get this issue when installing through CLI and GUI.
It sounds like you can't install Package B in Package A org because Package B depends on release 1.164 of Package A. That being the case, I'm guessing in the packaging org of Package B, you had v1.164 Package A installed when you created a release of Package B?
If that is the case, I'm not sure you're going to get out of that without releasing the dependency on Package A, in Package B.
Dependencies are likely caused as a result of referencing code or objects from Package A, in Package B. You could potentially release those dependencies by using dynamic SOQL/DML and potentially utilising the Callable interface if you're calling APIs.
Could you save yourself the time and install both into another Test org?
