Unmanaged package from namespaced Organization fails to install with lightning components
Trailblazer Community

Unmanaged package from namespaced Organization fails to install with lightning components

Apex , API , Packaging , Spring 15

Last updated 2021-07-09 ·Reference W-2489204 ·Reported By 4 users

In Review

On the attempted installation of an unmanaged package, which contains lightning components you are receiving:

"Your requested install failed. Please try this again.

None of the data or setup information in your salesforce.com organization should have been affected by this error.

If this error persists, contact salesforce.com Support through your normal channels and reference number: ##########"

The issue here is that the component will have a reference to the Developer Organizations namespace.

Note that when you are developing a Visualforce page within a namespace Developer Organization, if you typed in the namespace in front of the controller, on save we remove this for you. Currently for lightning components this is not occurring and then during installation of unmanaged packages, we cannot find that namespace in other Organizations and the installation fails to find the dependent component.

1) Create the following components in a namespaced Dev Org:

- Controller for lightning component:
public class CustController {
public static String getSomething() {
return 'HelloFromApex';

- Test class for above:
private class CustControllerTest {
static void testController() {
System.assertEquals('HelloFromApex', CustController.getSomething());

- Lightning component:
<aura:component controller="<OrgNamespace>.CustController">
<h1>Apex class is component controller</h1>

2) Create an unmanaged package and add the above lightning component. The controller should be automatically added to the package dependencies so just add the test class also.

3) Once ready click upload

4) Attempt an installation in another Org

As of now, it is recommended to use non-namespaced Organizations for unmanaged packages containing lightning components. For some components you can simply remove the namespace and treat the development as if it was not in a namespaced Organization as per the namespace usage examples and reference guide here:

NOTE: When you add the lightning component to the package, it will not auto find the dependencies as in the namespaced Developer Org we will be looking for dependency without namespace. Possibly create with the namespace, add to package including dependencies, then remove namespace in controller attribute prior to package upload to ensure all dependencies are added to the package.

Also please note that there are some components that this will not work for and you will notice this on save of the component. For example:

1) When adding a component into an app, the markup would be like so:

<!-- Add the component here -->
<namespace:myComponent />

2) Change the component code to the markup for an Organization with No Namespace and save in the Developer console:
<c:myComponent />

3) Close the App and reopen it in the Developer console and you will notice the namespace has been reverted back to the Organizations:

<!-- Add the component here -->
<namespace:myComponent />

Is it Fixed?

AP0 AP3 AP4 AP5 AP6 AP7 AP8 AP9 AP10 AP11 AP12 AP13 AP14 AP15 AP16 AP17 AP18 AP19 AP20 AP21 AP22 AP24 AP25 AP26 AP27 AP28 AUS1 AUS11 AUS2S AUS27 AUS26S AUS25 AUS24S AUS23 AUS22S AUS3 AUS43 AUS4S AUS5 AUS6S AUS7 AUS9 BRA1 BRA2S BRA4S CAN17S CAN1 CAN11S CAN2S CAN4S CAN6S CAN8S CS1 CS2 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 CS123 CS122 CS121 CS126 CS127 CS129 CS128 CS125 CS124 CS137 CS138 CS133 CS132 CS14 CS148 CS142 CS159 CS152 CS151 CS15 CS162 CS16 CS169 CS165 CS160 CS173 CS17 CS174 CS18 CS189 CS194 CS192 CS193 CS190 CS191 CS199 CS197 CS19 CS198 CS196 CS195 CS20 CS209 CS200 CS202 CS201 CS203 CS21 CS219 CS218 CS217 CS216 CS215 CS214 CS213 CS212 CS211 CS210 CS22 CS220 CS23 CS234 CS24 CS25 CS26 CS27 CS28 CS29 CS31 CS32 CS33 CS34 CS35 CS36 CS37 CS40 CS41 CS42 CS43 CS44 CS45 CS46 CS47 CS49 CS50 CS53 CS57 CS58 CS59 CS60 CS61 CS62 CS63 CS64 CS65 CS66 CS67 CS68 CS69 CS72 CS73 CS74 CS75 CS76 CS77 CS78 CS79 CS80 CS81 CS84 CS86 CS87 CS88 CS89 CS90 CS91 CS92 CS94 CS95 CS96 CS97 CS98 CS999 CS99 DEU1 DEU2S DEU4S EU16 EU17 EU18 EU19 EU25 EU26 EU27 EU28 EU29 EU30 EU31 EU32 EU33 EU34 EU35 EU36 EU37 EU38 EU39 EU40 EU41 EU42 EU43 EU44 EU45 EU46 EU47 EU48 FRA1 FRA2S FRA4S IND1 IND16S IND15 IND11 IND18S IND13 IND2S IND23 IND3S IND4S IND5 IND6S IND7 IND9 JPN1 JPN2S JPN3 JPN4S 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 NA149 NA146 NA147 NA148 NA154 NA158 NA159 NA153 NA151 NA155 NA152 NA150 NA156 NA161 NA163 NA167 NA160 NA166 NA165 NA169 NA164 NA168 NA162 NA172 NA170 NA174 NA171 NA173 NA196 NA202 NA204 NA21 NA218 NA214 NA217 NA215 NA64 NA65 NA66 NA68 NA69 NA70 NA71 NA72 NA73 NA74 NA75 NA76 NA77 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 UM8 UM9 USA1 USA2S USA3S USA4S

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.