Print this page

"Something went wrong" error in Community Builder

Knowledge Article Number 000240871
Resolution

Starting with the Winter'17 release, access check violations within custom lightning components are strictly enforced. These are the error messages you can encounter and how to fix them. You can learn more about Access Checks by reading our Developer Documentation.


Community Builder errors

 
  • Try refreshing the page. If that doesn't do the trick, describe what you were trying to accomplish to your Salesforce administrator. 
    Action failed: c$CloudCrazeComponent$cntroller$getHost [Cannot read property 'Qb' of undefined]
  • Try refreshing the page. If that doesn't do the trick, give your Salesforce administrator the following error ID, and describe what you were trying to accomplish.
    Error ID: b2e83d6e-63e9-422f-b532-0cfc9c393334
    Something has gone wrong. Error in $A.getCallback() [Cannot read property 'Qb' of undefined]
    Failling descriptor: {markup://c:CloudCrazeTopicRelatedProducts}. Please try again.
  • Try refreshing the page. If that doesn't do the trick, describe what you were trying to accomplish to your Salesforce administrator.
    Action failed: c$CloudCrazeComponent$cntroller$getHost [Cannot read property '$getTypeDefDescriptor$' of undefined]
  • Try refreshing the page. If that doesn't do the trick, give your Salesforce administrator the following error ID, and describe what you were trying to accomplish.
    Error ID: b2e83d6e-63e9-422f-b532-0cfc9c393334
    Something has gone wrong. Error in $A.getCallback() [Cannot read property '$getTypeDefDescriptor$' of undefined]
    Failling descriptor: {markup://c:CloudCrazeTopicRelatedProducts}. Please try again.

 

Errors in published community

Lightning Component's debug mode is disabled - If the page contains custom lightning components with access check errors, the page may or may not display depending on which component has failed and where it's located on the page. In situations where the error page isn't displayed, the rest of the page will still render with the exception of the component that has the error. 

Lightning Component's debug mode is enabled - The user won't be redirected to the error page. Instead, they'll see an infinite loading indicator. The page can also fail to load, depending on the location of the error in the component. If you have the browser's developer tools open, you'll see an output of any access check errors for the components.

 

Fix Something went wrong errors

 

The first step is to identify the component that is causing the issue.  This can be done by taking note of the component name in the error message dialog.  For the sample error message, “Action failed: c$CloudCrazeComponent$controller$getHost [Cannot read property '$getTypeDefDescriptor$' of undefined]”, the component is called c:CloudCrazeComponent, and the getHost() function within the controller javascript is causing the issue.

Open up the component within the Developer Console and analyze the code.  Follow the guidelines in the “Fixing Access Check Errors” section in our Developer Documentation to resolve the issues and save the changes.

Reload the Community Builder and access the page that was throwing the error to make sure the error dialog no longer appears.

Common problem

If an aura component’s controller or helper javascript file is accessing a component attribute that has not been defined in the component, the access check error will occur.  

In the example above where the “Action failed: c$CloudCrazeComponent$controller$getHost [Cannot read property '$getTypeDefDescriptor$' of undefined]” error is thrown, this was due to the component controller’s getHost() function calling component.set(“v.someAttribute”, “someValue”) when <aura:attribute name=”someAttribute” type=”..” ../> is not defined in the component.





promote demote