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
ram kiran verma gottumukklaram kiran verma gottumukkla 

quickActionHandlerHelper.js failed to create component - forceChatter:lightningComponent

folowing is the lighting code : 

<aura:component controller="ActivateAgreementController" implements="force:appHostable,flexipage:availableForAllPageTypes,flexipage:availableForRecordHome,force:hasRecordId,forceCommunity:availableForAllPageTypes,force:lightningQuickAction"  >
    <aura:handler name="init" value="{!this}" action="{!c.validateandactivateagreement}"/>
    <aura:attribute name="smsg" type="Boolean" default="false"/>
    <aura:attribute name="emsg" type="Boolean" default="false"/>
    <aura:attribute name="message" type="String"/>
    <aura:if isTrue="{!v.emsg}">
        <ui:message title="Error" severity="error" closable="false">
           Owner Update failed. Please try again later or contact your System Admin.
    <aura:if isTrue="{!v.smsg}">
        <ui:message title="Confirmation" severity="confirm" closable="false">

          ResultMessage:<ui:outputText value="{!v.message}"/>

           Successfully updated Owner.

    validateandactivateagreement : function(component, event, helper) {
        var action = component.get("c.agreementactivate");
        action.setParams({"id": component.get("v.recordId")});
        function(response) {
            var state = response.getReturnValue();
            if (state === true){
                component.set("v.smsg", true);
                 cmp.set("v.message", "hi");
            } else {
                 component.set("v.emsg", true);

global with sharing class ActivateAgreementController {
    public ActivateAgreementController(ApexPages.StandardController controller) {
    //Accepts the record id and sends a boolean status about the updation
    @AuraEnabled @RemoteAction
    global static Boolean agreementactivate(Id Agreementid){
            //Group oppQueue = [select Id from Group where  Type = 'Queue' AND DeveloperName = 'Opportunity_Review_Queue'];
            //Opportunity crec = [Select Id, OwnerId from Opportunity where Id=:oppid];
            //crec.OwnerId = oppQueue.Id;
            //update crec;
            contract contract_record = [select Record_Type_Name__c,AccountId,telia_TC_Party__c,telia_Customer_contact_person__c,telia_Sales_person__c 
                                        ,telia_Sales_responsible__c ,telia_Confidentiality_class__c,telia_Start_date__c ,telia_Signature_alternative__c
                                        ,CustomerSignedId ,CustomerSignedDate,telia_Customer_Signature_Place__c,Telia_Signed_By__c,Telia_Signed_Date__c,Signatories_Required__c from 
                                        contract where Id=:Agreementid];
           return true;
        catch(Exception e){
            return false;

its failling from quick action in lighting .error message : 
Unfortunately, there was a problem. Please try again. If the problem continues, get in touch with your administrator with the error ID shown here and any other related details.
Action failed: forceChatter:lightningComponent$controller$doInit [Error while creating content for lightning component quick action]
quickActionHandlerHelper.js failed to create component - forceChatter:lightningComponent
Michele ToscanoMichele Toscano
I am receiving this message as well:  
An internal server error has occurred
Error ID: 1713270143-4419952 (1964297404)
quickActionHandlerHelper.js failed to create component - forceChatter:lightningComponent

This just started today.  Code is the same as my other Org where it is working.  Did you receive any feedback on your issue?  I also noticed my debug logs are not generating in this same Org.  
Manoj ThangavelManoj Thangavel
Hi Michele,

Any fixes for the above Error? i am getting the same today?

Is it related to the permission issue?

Manoj T
I faced this issue today and the reason was that the controller of my component was not compiling. I had change a definition of a method that the controller was consuming, which made the controller invalid.
So I would suggest to compile all your classes when you have such issue to see if there is any compilation issue in your Org.