Find your content:

Search form

You are here

Issues rolling out new managed packages during the maintenance window


In the couple weeks between when Salesforce upgrades the first instances and when they have finished rolling the new version out to everyone, it is a struggle to get a new package out. Currently, our packaging org has been upgraded to Winter 13, but the orgs we have designated for QA are still sitting at Summer 12. So, the attempt at installation of a new package for testing in our QA org results in the following error:

Mismatching Versions

The AppExchange Application or component you have selected is not yet available on your instance of Please check back in a few days to retry the installation. Press the back button of your browser now and bookmark the AppExchange Directory page so that you can find it later.

Consequently, if we need to get an emergency release to a customer, they are out of luck if their org is still waiting for the new Salesforce release.

Is this something we just have to live with or is there a way to work around it?

Attribution to: Rob Scott

Possible Suggestion/Solution #1

We've run into this issue a number of times. Just recently again our release cycle coincided with the Summer '13 release cycle. Initial versions of some of our packages were packaged prior to the first Summer '13 upgrade weekend, so they were packaged under Spring '13. But our packager orgs were on nodes that were scheduled to be upgraded on the first weekend of the Summer '13 release. We wanted to push out these packages to some of our subscriber orgs on a limited basis. We had to make sure that we chose subscriber orgs that were going to be upgraded to Summer '13 in that first weekend, just to make sure that we would be able to re-package and upgrade them in the event we found critical bugs after our release.

I do not believe there is any workaround for this. The only thing I can recommend it to try not to have your package releases coincide with Salesforce releases.

Attribution to: tlfu

Possible Suggestion/Solution #2

I can't speak for Managed Packages, but I know that when using the ANT tool and with Changesets that the few weeks window as you have orgs across versions poses real challenges.

The only solution I've had is doing things like excluding components that are incompatible from the package.xml/changeset in order to get the release done and then manually configuring them if needed the target org.

If neither of those options are available in Managed Packages, you may be out of luck :(

Attribution to: Steven Herod

Possible Suggestion/Solution #3

You will need to modify the accompanying XML files to change the version back to the same as the one in production. You can also do this in the UI prior to creating a change set/pulling with ant.

Attribution to: Michael
This content is remixed from stackoverflow or stackexchange. Please visit

My Block Status

My Block Content