How to display Aura JS Errors Lightning OutHow to find out when Aura component / document is ready?How to...

Converting a sprinkler system's 24V AC outputs to 3.3V DC logic inputs

Is it idiomatic to construct against `this`

Is there any official lore on the Far Realm?

Is there really no use for MD5 anymore?

What makes accurate emulation of old systems a difficult task?

First time hit, with spinach? A little bit?

Which big number is bigger?

Do I have an "anti-research" personality?

Was there a shared-world project before "Thieves World"?

What is the most expensive material in the world that could be used to create Pun-Pun's lute?

Betweenness centrality formula

How exactly does Hawking radiation decrease the mass of black holes?

Critique of timeline aesthetic

Was there a Viking Exchange as well as a Columbian one?

Is the claim "Employers won't employ people with no 'social media presence'" realistic?

Checks user level and limit the data before saving it to mongoDB

Pre-plastic human skin alternative

Can we say “you can pay when the order gets ready”?

What happens to Mjolnir (Thor's hammer) at the end of Endgame?

Coordinate my way to the name of the (video) game

Pulling the rope with one hand is as heavy as with two hands?

How do I deal with a coworker that keeps asking to make small superficial changes to a report, and it is seriously triggering my anxiety?

A ​Note ​on ​N!

How can Republicans who favour free markets, consistently express anger when they don't like the outcome of that choice?



How to display Aura JS Errors Lightning Out


How to find out when Aura component / document is ready?How to handle errors in “e.recordSave” in lightning componentCreating a tab on a lightning component using aura and lightning design systemHow to navigate in lightning out?Intermittent 404 errors using Lightning Out in VisualforceDisplay spinner in specific component onlyLightning Out Event HandlingStreaming API in Lightning Component getCallback errorLightning component is hang for first timeLightning out - How to catch errors from the embedded component






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







2















I know I can wrap in a try / catch but the goal here is to display a useful error in cases where one was not expected..(programming error)



A basic lightning component displayed in a VF page using the standard app and component.



The only thing on the component is a lightning:spinner. The component has an init handler and the sole job of the init JS is to hide the spinner.



<aura:component description="test">
<aura:handler name="init" value="{!this}" action="{!c.doInit}"/>
<lightning:spinner variant="brand" aura:id="test_spinner"/>
</aura:component>


The controller



({
doInit : function(component,event,helper){
console.log('init');
helper.donothing(); //This does not exist and causes an error
$A.util.addClass(component.find("test_spinner"),'slds-hide');
}
})


Now when this runs it causes a framework error. The problem is that the user sees nothing. The spinner does not get hidden and the page just stalls...



Is there any way to display a message to the user instead of the entire component just stalling?



For some reason I seem to recall a component that could be used to display framework errors but I cannot seem to find it or I am just remembering incorrectly










share|improve this question





























    2















    I know I can wrap in a try / catch but the goal here is to display a useful error in cases where one was not expected..(programming error)



    A basic lightning component displayed in a VF page using the standard app and component.



    The only thing on the component is a lightning:spinner. The component has an init handler and the sole job of the init JS is to hide the spinner.



    <aura:component description="test">
    <aura:handler name="init" value="{!this}" action="{!c.doInit}"/>
    <lightning:spinner variant="brand" aura:id="test_spinner"/>
    </aura:component>


    The controller



    ({
    doInit : function(component,event,helper){
    console.log('init');
    helper.donothing(); //This does not exist and causes an error
    $A.util.addClass(component.find("test_spinner"),'slds-hide');
    }
    })


    Now when this runs it causes a framework error. The problem is that the user sees nothing. The spinner does not get hidden and the page just stalls...



    Is there any way to display a message to the user instead of the entire component just stalling?



    For some reason I seem to recall a component that could be used to display framework errors but I cannot seem to find it or I am just remembering incorrectly










    share|improve this question

























      2












      2








      2








      I know I can wrap in a try / catch but the goal here is to display a useful error in cases where one was not expected..(programming error)



      A basic lightning component displayed in a VF page using the standard app and component.



      The only thing on the component is a lightning:spinner. The component has an init handler and the sole job of the init JS is to hide the spinner.



      <aura:component description="test">
      <aura:handler name="init" value="{!this}" action="{!c.doInit}"/>
      <lightning:spinner variant="brand" aura:id="test_spinner"/>
      </aura:component>


      The controller



      ({
      doInit : function(component,event,helper){
      console.log('init');
      helper.donothing(); //This does not exist and causes an error
      $A.util.addClass(component.find("test_spinner"),'slds-hide');
      }
      })


      Now when this runs it causes a framework error. The problem is that the user sees nothing. The spinner does not get hidden and the page just stalls...



      Is there any way to display a message to the user instead of the entire component just stalling?



      For some reason I seem to recall a component that could be used to display framework errors but I cannot seem to find it or I am just remembering incorrectly










      share|improve this question














      I know I can wrap in a try / catch but the goal here is to display a useful error in cases where one was not expected..(programming error)



      A basic lightning component displayed in a VF page using the standard app and component.



      The only thing on the component is a lightning:spinner. The component has an init handler and the sole job of the init JS is to hide the spinner.



      <aura:component description="test">
      <aura:handler name="init" value="{!this}" action="{!c.doInit}"/>
      <lightning:spinner variant="brand" aura:id="test_spinner"/>
      </aura:component>


      The controller



      ({
      doInit : function(component,event,helper){
      console.log('init');
      helper.donothing(); //This does not exist and causes an error
      $A.util.addClass(component.find("test_spinner"),'slds-hide');
      }
      })


      Now when this runs it causes a framework error. The problem is that the user sees nothing. The spinner does not get hidden and the page just stalls...



      Is there any way to display a message to the user instead of the entire component just stalling?



      For some reason I seem to recall a component that could be used to display framework errors but I cannot seem to find it or I am just remembering incorrectly







      lightning-aura-components lightning






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 3 hours ago









      EricEric

      45.5k754130




      45.5k754130






















          1 Answer
          1






          active

          oldest

          votes


















          3














          There is a display element; it shows up at the very bottom of the page. This happens in Lightning Out automatically. It's not styled by default, as far as I can tell, so you might want to add some style to it. The message is in a div#auraErrorMessage element. Try starting with this:



          <style>
          div#auraErrorMessage {
          position: fixed;
          text-align: center;
          white-space: pre-line;
          padding-top: calc(25vh - 3em);
          height: 50vh;
          top: 25vh;
          left: 25vw;
          right: 25vw;
          z-index: 1000;
          border: 5px solid red;
          }
          </style>


          You could attach a DOM mutation event to this element to detect new messages, etc as well.



          I'm not aware of a specific way to otherwise handle errors in Lightning Out; this is normally handled by the App (e.g. one.app), but it's not documented how/if we can do this externally.






          share|improve this answer
























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "459"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f260272%2fhow-to-display-aura-js-errors-lightning-out%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            3














            There is a display element; it shows up at the very bottom of the page. This happens in Lightning Out automatically. It's not styled by default, as far as I can tell, so you might want to add some style to it. The message is in a div#auraErrorMessage element. Try starting with this:



            <style>
            div#auraErrorMessage {
            position: fixed;
            text-align: center;
            white-space: pre-line;
            padding-top: calc(25vh - 3em);
            height: 50vh;
            top: 25vh;
            left: 25vw;
            right: 25vw;
            z-index: 1000;
            border: 5px solid red;
            }
            </style>


            You could attach a DOM mutation event to this element to detect new messages, etc as well.



            I'm not aware of a specific way to otherwise handle errors in Lightning Out; this is normally handled by the App (e.g. one.app), but it's not documented how/if we can do this externally.






            share|improve this answer




























              3














              There is a display element; it shows up at the very bottom of the page. This happens in Lightning Out automatically. It's not styled by default, as far as I can tell, so you might want to add some style to it. The message is in a div#auraErrorMessage element. Try starting with this:



              <style>
              div#auraErrorMessage {
              position: fixed;
              text-align: center;
              white-space: pre-line;
              padding-top: calc(25vh - 3em);
              height: 50vh;
              top: 25vh;
              left: 25vw;
              right: 25vw;
              z-index: 1000;
              border: 5px solid red;
              }
              </style>


              You could attach a DOM mutation event to this element to detect new messages, etc as well.



              I'm not aware of a specific way to otherwise handle errors in Lightning Out; this is normally handled by the App (e.g. one.app), but it's not documented how/if we can do this externally.






              share|improve this answer


























                3












                3








                3







                There is a display element; it shows up at the very bottom of the page. This happens in Lightning Out automatically. It's not styled by default, as far as I can tell, so you might want to add some style to it. The message is in a div#auraErrorMessage element. Try starting with this:



                <style>
                div#auraErrorMessage {
                position: fixed;
                text-align: center;
                white-space: pre-line;
                padding-top: calc(25vh - 3em);
                height: 50vh;
                top: 25vh;
                left: 25vw;
                right: 25vw;
                z-index: 1000;
                border: 5px solid red;
                }
                </style>


                You could attach a DOM mutation event to this element to detect new messages, etc as well.



                I'm not aware of a specific way to otherwise handle errors in Lightning Out; this is normally handled by the App (e.g. one.app), but it's not documented how/if we can do this externally.






                share|improve this answer













                There is a display element; it shows up at the very bottom of the page. This happens in Lightning Out automatically. It's not styled by default, as far as I can tell, so you might want to add some style to it. The message is in a div#auraErrorMessage element. Try starting with this:



                <style>
                div#auraErrorMessage {
                position: fixed;
                text-align: center;
                white-space: pre-line;
                padding-top: calc(25vh - 3em);
                height: 50vh;
                top: 25vh;
                left: 25vw;
                right: 25vw;
                z-index: 1000;
                border: 5px solid red;
                }
                </style>


                You could attach a DOM mutation event to this element to detect new messages, etc as well.



                I'm not aware of a specific way to otherwise handle errors in Lightning Out; this is normally handled by the App (e.g. one.app), but it's not documented how/if we can do this externally.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered 2 hours ago









                sfdcfoxsfdcfox

                267k13213461




                267k13213461






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Salesforce Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f260272%2fhow-to-display-aura-js-errors-lightning-out%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    “%fieldName is a required field.”, in Magento2 REST API Call for GET Method Type The Next...

                    How to change City field to a dropdown in Checkout step Magento 2Magento 2 : How to change UI field(s)...

                    變成蝙蝠會怎樣? 參考資料 外部連結 导航菜单Thomas Nagel, "What is it like to be a...