When a user upgraded to the latest version of my managed package his installation failed as he required another package.

Yes this package is indeed installed in my packaging org but not referenced by my managed metadata. Magically my package also in the Force IDE now shows Referenced Packages.

I can absolutely make no sense out of it, as I can neighter find Components of those other packages in my package nor does any of the critical files e.g. package.xml contain references.

Please help!

  • 2
    Have you tried uninstalling this other package from your Managed Package DE org? If there are true dependencies, these should be presented to you when attempting to uninstall, and should prevent the uninstall from succeeding. Also, on your managed package's detail page, does the "Type" field now show "Managed(Extension)" ?
    – zachelrath
    Commented Jan 17, 2014 at 15:58

1 Answer 1


I daresay it may have been an accidental reference; it's easier than you think to form a reference. For example, if you have package A installed, and you're developing package B, and package B has a page layout that includes a custom link or custom field from package A, then you've automatically formed a reference.

The reference doesn't have to exist in package.xml in order for you to create an extension package. All it takes is any simple configuration anywhere in package B referencing package A and you'll have your reference. Check the list of items in package B, and see if anything there is from package A. It should let you know right on the list.

Your best bet is to uninstall any version of your package where it became an extension (if you've uploaded it/installed it anywhere), and request that salesforce.com roll the package back into a beta on the last version you had where it was not an extension; this should undo the Managed (Extension) status. Short of this, you'll be required to create an entirely new managed package, which will definitely be nothing short of an inconvenience.

Finally, as noted in the comments, you could try uninstalling package A, and see what errors you get. You'll be advised as to which elements caused the dependency.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .