My package is on a developer organization, it's marked as managed, and the namespace is FBO. I've uploaded the package and I can install it successfully through the URL. Since I need to automate the installation, I'm using the metadata API.
When I install my managed package through the metadata API into other Salesforce instances, the deployment result is a success but it says that no components were installed, and no failures. My zip file has the folder "unpackaged" which contains the file "package.xml" and the folder "installedPackages". That folder has "fbo.installedPackage" inside it.
Here are my file contents:
unpackaged/package.xml:
<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
<types>
<members>*</members>
<name>InstalledPackage</name>
</types>
<version>52.0</version>
</Package>
unpackaged/installedPackages/fbo.installedPackage:
<?xml version="1.0" encoding="UTF-8"?>
<InstalledPackage xmlns="http://soap.sforce.com/2006/04/metadata">
<versionNumber>1.0</versionNumber>
<activateRSS>false</activateRSS>
</InstalledPackage>
I've been beating my head against this and can't find anyone else running into a similar issue. I can install other managed pacakges through my metadata client on the target org, just not the one I'm developing.
Best Answer
I don't know if this will help you, but I successfully installed your package. Keep in mind that literally everything in the Metadata API is case sensitive. Here is the ZIP that I used to install your package:
Save this to a file like "example.b64", then decode this with the command:
Then decompress:
And then try deploying:
You can also compare the files to my own and see if there's any difference.
These commands were ran from Github Bash Shell (included in Github Desktop), using
sfdx-cli/7.110.0 win32-x86 node-v14.17.0