Why am I getting the error Mismatching Versions?
|Knowledge Article Number||000212675|
Why am I getting the following errors when trying to install a package from the AppExchange or when deploying a change set?
The AppExchange Application or component you have selected is not yet available on your instance of salesforce.com. 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.
One or more components failed Version Compatibility Check. This change set contains components that require the "[VersionNumberHere]" or higher.
All components failed Version Compatibility Check. Every component in this change set requires the "[VersionNumberHere]" or higher platform version. Please select an organization with a platform version of "[VersionNumberHere]" or higher.
|Resolution||This error occurs when you try to install the latest version of an app/package onto an instance that hasn't been updated to the newest Salesforce release yet. This is an expected behavior. The best solution is to wait for your instance to be upgraded to the current release.
Example 1: You are trying to install a package developed on a Spring '16 instance in an org running Winter '16.
The developer of the app may be able to provide you with an installation link for an older version of the app that can be installed on your organization.
Example 2: You are trying to deploy a change set developed on a Winter '16 sandbox to an org running Summer '15.
If you are getting the error when deploying a change set, this means that you are deploying a component that has been introduced on a new release and isn't available on the target org.
Please understand that the preview sandboxes are mainly used in order to test out the new features and there are compatibility issues when deploying to an older release version. This is why we recommend that these should not be used for deployment since there are features that are not available on older releases.
This is an expected behavior. The best solution is to wait for your instance to be upgraded to the current release.
You can find information on which instance have been updated on TRUST.
Outbound Change Set Validation Errors
Uploading Change Sets During Staggered Salesforce Service Upgrades