function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
VarunCVarunC 

Lightning Component app throwing Internal Server Error

I've a Lightning Component that works fine in dev org but deployed in a managed package it throws Internal Server Error. I found another developer thread that has expereinced same kind of error with Lightning Component -
http://salesforce.stackexchange.com/questions/100990/an-internal-server-error-has-occurred-error-id-143631613-25605-15667340

I'm looking to find out if my issue is due to same and I've no idea what this Error ID means, no more details are shown.

My error details are:
An internal server error has occurred Error ID: 1288557852-29109 (-898570520)



 
pconpcon
Anytime you get an Internal Server Error (ISE) the only real way to decifier what the error means is to contact Salesforce support and provide what you were doing as well as the Error Id.
VarunCVarunC
I always do but my case always gets closed citing they dont provide Developer Support in basic support and we need premier support even to find out what the Internal Server Error is about. :-(
pconpcon
You can always use a binary search and comment out your code until you figure out what line is causing your ISE.
VarunCVarunC
That is what I've been doing. The component has Apex class connection, js controller, helper js and component markup and so many lines of code. Moreover the issue is not happening in dev org, its when I package the component and install in another org for testing, that's where the Internal Server Error occurs. In dev org the component is working perfectly fine. And thus its become completely unrealistic to make line by line addition or removal and upload and then install in another org to test.
Jacob Friedman 11Jacob Friedman 11
I'm having this issue two years later!  Were you able to work around this?  If so, what did you do?
VarunCVarunC
For me, it was date entry field I was populating on load. I was missing setting up a padded month/date value so I was required to fill both day and month value with 2 digit format, and that fixed it for me. But yes, you should approach SFDC support with Error ID, that is the best way, otherwise, it is just needle in the haystack, and you got to debug everything line by line yourself and pinpoint faulty code. *- Varun*