2

We are getting the following error when attempting to deploy an UN-changed version of an AuraDefinitionBundle to one of our Patch orgs using the Force.com Migration Tool:

UNKNOWN_EXCEPTION: Managed Package Patch Modification Exception: A change was made to the patch release that will change the visible behavior of the application: You can't delete managed-released components in a patch release

This is only happening when trying to deploy one of our AuraDefinitionBundle files. We have not made any changes to any portions of this bundle at all, so we are very confused why we are getting this error, and it is causing our automated Continuous Integration builds to this patch org to fail.

As proof that we have not modified anything in this file, we retrieved the file exactly as it is from the org, then redeployed it unchanged. That is, we used the Force.com Migration Tool's ant retrieveUnpackaged default command with a package.xml like the following:

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types>
        <members>SomeBundleName</members>
        <name>AuraDefinitionBundle</name>
    </types>
    <version>35.0</version>
</Package>

And then immediately used ant deployUnpackaged to deploy what was retrieved right back to the same org. And we got the above error.

Any ideas?

7
  • Try saving each components one by one to discover which component is failing .Lightning is still evolving so something might have broken some of the components . Mar 8, 2016 at 14:34
  • @MohithShrivastava I know exactly which component is failing. The component I'm trying to retrieve / deploy unchanged is the only one that is failing.
    – zachelrath
    Mar 8, 2016 at 19:08
  • Is it compiling atleast when you try to save ? Mar 8, 2016 at 19:13
  • @zachelrath did you every resolve this issue? Have the exact same issue in a patch org of ours. Mar 29, 2016 at 13:20
  • @StephenRoden Nope, we submitted a case but Partner Support closed the issue as being "Out of Scope". We circumvented the issue by excluding that file from our CI deployment to the particular patch org --- since the file was unmodified it was not a problem to exclude it. But this approach is obviously unsustainable.
    – zachelrath
    Apr 7, 2016 at 15:59

1 Answer 1

0

Salesforce acknowledged that this is a bug on their Known Issues site, which is "In Review" as of July 29, 2016:

Salesforce Known Issue: "You can't delete managed-released components in a patch release" error when AuraDefinitionBundle which isn't modified is deployed to patch org

You must log in to answer this question.

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