Salesforce lightning: "TypeError: action.$getComponent$ is not a function" exception around $A.enqueueAction(action);

Question

This gave me over 5 hours of brain damage, and yet don't have a solution. Can someone please assist?

UPDATE: markup in component:

<td>
    <div class="slds-truncate" >
        <a href="javascript:void(0);" onclick="{!c.nextStage}">Complete</a>
    </div>
</td>

UPDATE: controllerJS function:

nextStage: function(component, event, helper){
        console.log("----------------> nextStage 0");
        helper.completeStage(component, event, helper);               
    },

helperJS function:

completeStage : function(component, event, helper){
        console.log('---------------> completeStage 1 ');
        var action = component.get("c.uselessMethod");

        action.setCallback(this, function(response) {
            console.log('---------------> completeStage 2');
        });

        try{
            $A.enqueueAction(action);
        }
        catch(err3){
            console.log("---------------> completeStage EXCEPTION " + err3);
        }
    },

This is my apex controller method:

@AuraEnabled
    public static void uselessMethod(){
        system.debug(logginglevel.error,'------------------------------------> uselessMethod! ');
    }

Browser Console Log:

---------------> completeStage 1 
---------------> completeStage EXCEPTION TypeError: action.$getComponent$ is not a function

The callback is not being invoked at all. $A.enqueueAction(action) is generating an exception. No Apex debug log either. My web search yielded irrelevant results.

Answer 1

I suspect this error might be caused by a variety of issues, but as Tony White mentioned, I was encountering this in a concrete component that extended an abstract component, that extended another abstract component.

I fixed this issue by making sure the API versions of all three components were the same. The concrete component was set to an API version of 40, where as the other components were API 38 and API 39. Setting all versions to API 39 resolved it.

Answer 2

Sometimes the component gets corrupt and starts giving this issue as well. There is no mistake in your code just try calling the same things in a new component and I can assure it will work well.