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

Improve this question
8
  • 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, 2018 at 13:41
  • 1
    ah that is a shame - I shall spin up another dev org for testing purposes, thanks :)
    – D Woodcock
    Aug 28, 2018 at 14:02
  • 1
    Looks very similar to this KI from last summer's release... success.salesforce.com/…
    – BritishBoyinDC
    Aug 28, 2018 at 14:04
  • 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, 2018 at 3:17
  • 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, 2018 at 8:13

1 Answer 1

Reset to default
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.

Improve this answer
4
  • Unfortunately all CS* instances are currently showing as Patch 19.0 :(
    – jkraybill
    Aug 30, 2018 at 0:20
  • And all scratch orgs use CS Instances as far as I know? So right now, I can't install packages into my scratch orgs to do any testing...
    – BritishBoyinDC
    Aug 30, 2018 at 13:02
  • 1
    I was just able to install a package that previously failed into a new scratch org, so looks like the updates being pushed out might be resolving this issue?
    – BritishBoyinDC
    Aug 30, 2018 at 18:03
  • As per How can I tell what is changing in Salesforce as they patch each pod? - I couldn't find any public known issues for 214019100. Only 214019000
    – Daniel Ballinger
    Aug 30, 2018 at 19:58

You must log in to answer this question.

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