Package upgrade can fail with an unknown property which does not exist in the package
Trailblazer Community

Package upgrade can fail with an unknown property which does not exist in the package

Apex , Packaging , VisualForce

Last updated 2019-10-12 ·Reference W-6281372 ·Reported By 10 users

Fixed - Winter '20

Summary
If a package upgrade failed and if the second round of the upgrade attempt is done with a different version from the one used in the previous failed upgrade, a compile info of an apex component which has been created at the first upgrade attempt could be used while compiling apex components in the second upgrade. It could make the second upgrade attempt fail with the "Unknown property" errors. And the name of the properties in the error messages will show properties which does not exist in the package used in the second upgrade attempt.

Repro
1. Create the package of version 1.0.

1-1. On a developer org, create 2 apex classes which are used as controllers.

public class MyComponentController {
}

public class MyOuterComponentController {
}

1-2. Create 2 apex components which uses previous apex classes as controllers, and make one of them refer to another. Name them as "MyComponent" and "MyOuterComponent".

"MyComponent"

<apex:component controller="MyComponentController">
</apex:component>

"MyOuterComponent"

<apex:component controller="MyOuterComponentController">
<c:MyComponent />
</apex:component>

1-3. Create a test class for controllers.

@isTest private class TestClazz {
testmethod static void dotest() {
MyComponentController c = new MyComponentController();
MyOuterComponentController oc = new MyOuterComponentController();
}
}

1-4. Create a managed package, add them all to it, and upload it as 1.0.

2. Create the package of version 1.1.

2-1. Modify "MyOuterComponentController" and add a property.

public class MyOuterComponentController {
public String str { get; set; }
}

2-2. Modify "MyOuterComponent" so that it refers to the property previously added.

<apex:component controller="MyOuterComponentController">
<apex.outputTest value="{!str}" />
<c:MyComponent />
</apex:component>

2-3. Modify "MyComponent" so it outputs something.

<apex:component controller="MyComponentController">
This is my page. <br/>
</apex:component>

2-4. Modify the test class so that it covers the newly added code.

@isTest private class TestClazz {
testmethod static void dotest() {
MyComponentController c = new MyComponentController();
MyOuterComponentController oc = new MyOuterComponentController();
System.debug(oc.str);
}
}

2-5. Upload the package as 1.1.

3. Create the package of version 1.2.

3-1. Modify "MyComponentController" and add a new property.

public class MyComponentController {
public String aNewProperty { get; set; }
}

3-2. Modify "MyComponent" so that it refers to the property previously added.

<apex:component controller="MyComponentController">
<apex:outputPanel rendered="{!AND(aNewProperty != null)}">
This is my page.
</apex:outputPanel>
</apex:component>

3-3. Create an install handler which throws an exception so that the upgrade fails.

global class MyInstallHandler implements InstallHandler {
global void onInstall(InstallContext context) { throwException(); }

public void throwException() {
Account acc = [select name from account where name = 'NeverExists']; // it should throw an exception.
}
}

4. On a subscriber org, install the package 1.0.

5. On the subscriber org, try upgrading the package from 1.0 to 1.2. It should fail with the "The post install script failed." error, and the installed package version is still 1.0.

6. On the subscriber org, try upgrading the package from 1.0 to 1.1. You will see that the upgrade fails due to the unknown property of MyComponentController.aNewProperty which does not exist in the package 1.1, as follows:

Exception type: class core.mfpackage.install.HandledPackageInstallException
Exception msg: moduleapi.isv.packaging.exception.PackageInstallException: 00Dxx0000001gkn: Multiple install problems encountered [null: Unknown property 'MyComponentController.aNewProperty': MyOuterComponent: Unknown property 'MyComponentController.aNewProperty']
Stack trace:
core.mfpackage.install.HandledPackageInstallException: moduleapi.isv.packaging.exception.PackageInstallExcep

Workaround
Split the deployment into two:

- First deployment contains Apex classes and Visualforce pages
- Second deployment contains the Visualforce components


This issue is due to an internal bug related to cache processing.

Is it Fixed?

AP0 AP3 AP4 AP5 AP6 AP7 AP8 AP9 AP10 AP11 AP12 AP13 AP14 AP15 AP16 AP17 AP18 AP19 AP20 AP21 AP22 AP28 CS1 CS2 CS3 CS4 CS5 CS6 CS7 CS8 CS9 CS10 CS109 CS108 CS107 CS106 CS105 CS102 CS101 CS100 CS115 CS119 CS110 CS117 CS114 CS113 CS112 CS111 CS11 CS116 CS12 CS122 CS121 CS126 CS127 CS129 CS128 CS125 CS124 CS123 CS137 CS138 CS13 CS133 CS132 CS14 CS148 CS142 CS159 CS152 CS151 CS15 CS165 CS16 CS169 CS17 CS18 CS194 CS19 CS198 CS196 CS195 CS20 CS21 CS22 CS23 CS24 CS25 CS26 CS27 CS28 CS29 CS30 CS31 CS32 CS33 CS34 CS35 CS36 CS37 CS40 CS41 CS42 CS43 CS44 CS45 CS47 CS50 CS51 CS52 CS53 CS54 CS57 CS58 CS59 CS60 CS61 CS62 CS63 CS64 CS65 CS66 CS67 CS68 CS69 CS70 CS71 CS72 CS73 CS74 CS75 CS76 CS77 CS78 CS79 CS80 CS81 CS82 CS83 CS84 CS85 CS86 CS87 CS88 CS89 CS90 CS91 CS92 CS94 CS95 CS96 CS97 CS98 CS99 EU7 EU8 EU10 EU12 EU13 EU14 EU15 EU16 EU17 EU18 EU19 EU25 EU26 EU27 EU28 EU29 EU30 EU31 EU32 NA104 NA107 NA109 NA100 NA101 NA103 NA102 NA105 NA119 NA116 NA110 NA118 NA112 NA111 NA115 NA114 NA113 NA117 NA125 NA124 NA122 NA120 NA126 NA127 NA123 NA129 NA121 NA128 NA138 NA134 NA133 NA136 NA135 NA132 NA131 NA130 NA137 NA139 NA140 NA142 NA141 NA146 NA147 NA148 NA154 NA155 NA172 NA174 NA171 NA173 NA196 NA21 NA46 NA47 NA49 NA52 NA54 NA57 NA58 NA59 NA61 NA62 NA64 NA65 NA66 NA67 NA68 NA69 NA70 NA71 NA72 NA73 NA74 NA75 NA76 NA77 NA79 NA80 NA81 NA82 NA83 NA84 NA85 NA86 NA87 NA88 NA89 NA90 NA91 NA92 NA93 NA94 NA95 NA96 NA97 NA98 NA99 UM1 UM2 UM3 UM4 UM5 UM6 UM7

Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.