0

This post from nearly three years ago says that Stack Exchanging is a viable option for troubleshooting gacks. Clicking the Upload button on a managed package is throwing the following GACK:

Error ID: 745113341-129879 (1384210970)

All code compiles without issue deploying and in UI with Compile link on Apex Classes page. All tests pass too.

Any guidance on the core underlying issue is greatly appreciated. Thanks!

2
  • 1
    I don't feel the statement "Stack Exchanging is a viable option for troubleshooting GACKs" is entirely genuine. That official developer blog article that you linked to says that Salesforce support will be able to see a question here, but that still implies that you're working directly with Salesforce's customer support. I believe that most of the contributors here (myself included) are customers of Salesforce (rather than employees of Salesforce), and pretty much the only people capable of making use of the GACK error Ids are Salesforce employees.
    – Derek F
    Apr 25, 2018 at 18:51
  • Had this happen when a lightning component referenced a property that no longer existed. Only sf can tell you for sure
    – Eric
    Apr 26, 2018 at 4:54

2 Answers 2

1

You need to submit a case to find out more. Most likely, the packaging system missed a dependency that was later found during the upload process, or you've accidentally included an unsupported metadata type in your package. It's rare, but it does happen. One thing you could try besides going through support, is to pull your package to a Force.com IDE or another tool, and try to deploy your entire package to a sandbox, scratch org, or new developer org, and see if it deploys okay. If it complains about any missing dependencies, you'll need to add those to your package and try again.

0

I don't know, if it's going to help someone, but for me, the cause was strange. I've created deep nested LWC component folders in my project (for better management of code). i.e.

force-app > main > default > lwc > cmp1 > lwc > cmp2 > lwc > cmp3 > lwc > cmp4 > lwc > cmp5 > lwc > cmp6 > lwc

The last LWC component was the reason for the GACK error. I changed the relationship for cmp6 from being a child of cmp5 to being a sibling of cmp5 . Hope this helps! cheers.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.