13

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

D Woodcock
  • 133
  • 4
  • 1
    I believe this a bug - I hit the same issue yesterday, and have raised a case with support - I'll update here if I get any updates. But I would try installing it in a regular dev org if you can - seems to be a Sandbox issue – BritishBoyinDC Aug 28 '18 at 13:41
  • 1
    ah that is a shame - I shall spin up another dev org for testing purposes, thanks :) – D Woodcock Aug 28 '18 at 14:02
  • 1
    Looks very similar to this KI from last summer's release... https://success.salesforce.com/issues_view?id=a1p3A0000008jMrQAI&title=package-install-fails-with-error-no-controller-named-js-xxxxxx-found-or-we-couldn-t-retrieve-the-design-time-component-information-for-component – BritishBoyinDC Aug 28 '18 at 14:04
  • It does, I came across this earlier in my search for answers before asking the question on here. Your dev org solution does the job. – D Woodcock Aug 28 '18 at 15:22
  • 1
    I can confirm that we began seeing this too as of yesterday, EXACT same symptom. All sandbox instances fail, all production/dev/test instances work fine. I found at least 3 past known issues on the Salesforce known issues page from past releases that were all marked as resolved, but it's obviously happened again. If Salesforce posts a "Known Issue" for this one, please post it here so we can upvote it. – jkraybill Aug 29 '18 at 03:17
  • It's happening to us too. I hope they fix this soon. – Tyler Kauffman Aug 28 '18 at 16:40
  • 1
    One thing to check would be the release version that the orgs that work are on vs the version of the sandboxes that are failing. Sounds like the problem is to sandboxes, but it might reveal something. E.g. It might be specific to Summer '18 Patch 19.0 that is showing up on most sandboxes. Most other orgs are on Summer '18 Patch 18.7 – Daniel Ballinger Aug 29 '18 at 06:25
  • 2
    I have just checked the release version for the orgs as @DanielBallinger has suggested. The sandbox is running patch 19 and the dev orgs + enterprise org used for testing and demos are running patch 18.7. – D Woodcock Aug 29 '18 at 08:13

1 Answers1

4

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.

Daniel Ballinger
  • 102,288
  • 39
  • 270
  • 594