Last update: 9 September 2019, 17:10 BST
We're aware of an issue with the update to Winter '20 that Salesforce rolled out over the weekend which is causing API retrieval issues.
What's the issue?
With the latest Winter '20 upgrade, there appear to have been some breaking changes in backwards compatibility for metadata API retrieval requests.
What orgs does it affect?
Some orgs upgraded to Winter '20 - so far this is primarily sandboxes. It does not seem to affect newly created preview orgs.
What's the impact?
Comparisons and deployments in Gearset using any affected org as either source or target will fail with an error.
Is there a workaround with Gearset?
UPDATE (13:16 BST) - We have now released a workaround for this issue. Removing
Site.com from your metadata filter should resolve the issue. If you continue to have problems with Winter '20 orgs and removing
Site.com from your metadata filter does not fix the issue, please contact us.
There appear to be two different issues occurring. One of them appears to be related to the
Site.com metadata type, and you may be able to work around the issue by excluding this type from your metadata filter.
The other issue appears to be related to metadata in unlocked packages. Removing any metadata types for which you have unlocked package metadata from your metadata filter may fix the issue. However, this may include the majority of types, depending on your unlocked packages.
Is there anything else I can do?
Contacting Salesforce support will help flag this issue to them so they can prioritise a fix. This change won't just affect Gearset, it'll affect any tool which requests metadata over the API.
What is Gearset doing?
We've released a workaround for this issue which should allow you to run comparisons and deployments against affected orgs. We'll keep investigating and updating this article and the app with any further developments.