Issue with custom-activity: runtime error: invalid memory address or nil pointer dereference about flogo-contrib HOT 6 CLOSED

Hi @mgdevstack it seems like your activity.json in https://github.com/mgdevstack/flogo-contrib/tree/master/activity/simpletest is missing the "ref" property. Try with this:
{
"name": "simpletest",
"version": "0.0.1",
"type": "flogo:activity",
"ref": "github.com/mgdevstack/flogo-contrib/activity/simpletest",
"description": "Simple Activity to test",
"author": "Mayank Gaikwad [email protected]",
"inputs":[
{
"name": "input",
"type": "string"
}
],
"outputs": [
{
"name": "output",
"type": "string"
}
]
}

from flogo-contrib.

@torresashjian, Can you please have look on this as a priority issue. None of my applications are running due to this error where custom activities are involved in the flow.

I tried using docker UI to install my custom activities but it shows "install successful" but activities are not visible in UI to add.

Reference: https://github.com/mgdevstack/flogo-contrib/tree/master/activity/pahoMQTT

from flogo-contrib.

@torresashjian, I tried with above fix, but it's not working.
mgdevstack@c007178

As in application's flogo.json, activityref is already provided. I don't think, ref in activity.json should hold any importance. (As we first create activity with flogogen and then push to github / central repo)
i.e. https://github.com/mgdevstack/flogo/blob/098bb642733ce8f7d38939e72fe92653b21ef355/apps/simpleapp/flogo.json#L45

Any other points to debug?

from flogo-contrib.

Thanks @torresashjian, I hope, the problem is resolved with your suggestion. If ref attribute in activity.json is the reason behind this issue, we need to fix codebase to pick up activity reference from application's flogo.json (activityRef attribute) not from activity.json (ref attribute) because as earlier mentioned, we create activity first, push this to git and then reference this activity in the application.

Is it worth doing?

from flogo-contrib.

@mgdevstack was your issue resolved? will look into the feasibility around your suggestion. perhaps @fm-tibco has some thoughts?

from flogo-contrib.

Closing with the assumption that the issue is solved... opened a new issue TIBCOSoftware/flogo#183 to track @mgdevstack's suggestion around ref

from flogo-contrib.