Install Managed Package Into Sandbox Fails on All Lightning Component Bundles

I have developed an app for the Salesforce platform and have successfully created a beta managed package ready for testing on one of our sandboxes. however when I try to install the package on the sandbox, it fails with a large number of errors detailing that every part of a lightning bundle does not exist. This same error happened when attempting to install a dependency app from the App Exchange directly into the sandbox, but I got around this by installing it into the Test Enterprise Org.

does anyone know why this happens when trying to install to a sandbox? How can I get around this problem with a beta managed package?

This is a portion of the 58 errors that I receive:

1.  No EVENT named markup://it4sxr:SourceAddedEvent found
SourceAddedEvent: No EVENT named markup://it4sxr:SourceAddedEvent found

2.  No CONTROLLER named js://it4sxr.SourceList found
SourceListController: No CONTROLLER named js://it4sxr.SourceList found

3.  No HELPER named js://it4sxr.SourceList found
SourceListHelper: No HELPER named js://it4sxr.SourceList found

4.  No STYLE named css://it4sxr.SourceList found
SourceList: No STYLE named css://it4sxr.SourceList found

5.  No COMPONENT named markup://it4sxr:SourceList found
SourceList: No COMPONENT named markup://it4sxr:SourceList found

6.  No CONTROLLER named js://it4sxr.ImportJobService found
ImportJobServiceController: No CONTROLLER named js://it4sxr.ImportJobService found

7.  No HELPER named js://it4sxr.ImportJobService found
JobServiceHelper: No HELPER named js://it4sxr.ImportJobService found

8.  No COMPONENT named markup://it4sxr:ImportJobService found
ImportJobService: No COMPONENT named markup://it4sxr:ImportJobService found

Thanks

Answer

Since it seems to be an internal Salesforce bug there isn’t much you can do about it until they resolve it.

They are onto it:

Team is looking into it right now. W-5394323 for reference if you have a support case or talk to a support agent.
Farhan Tahir


Circumstantial evidence suggests Summer’17 Patch 19.0 could be responsible. So if you can avoid deploying to orgs with that patch version you can avoid the problem. YMMV.

Attribution
Source : Link , Question Author : D. Woodcock , Answer Author : Daniel Ballinger

Leave a Comment