getActivityInfo activityName parameter does not seem to work

[ericblade]

After creating an activity "testActivity" using configurator, I rebooted, and attempted to determine that the activity was in fact installed:

# luna-send -n 1 -f luna://com.webos.service.activitymanager/getManagerInfo '{}' | grep testActivity
                    "name": "testActivity"
# luna-send -n 1 -f luna://com.webos.service.activitymanager/getActivityInfo '{"activityName":"testActivity"}'
{
    "errorCode": 2,
    "returnValue": false,
    "errorText": "Activity name/creator pair not found"
}
# luna-send -n 1 -f luna://com.webos.service.activitymanager/getManagerInfo '{}' | grep testActivity
                    "name": "testActivity"
# 

The activity then ran a couple of minutes later.

[Tofee]

When using luna-send, you will also have to specify an application name with "-a". Indeed, getActivityInfo will also compare the "creator" of the LS2 message, whose name has to match the creator of the activity at the time of its registering.
This additional comparison is skipped if the LS2 message is sent anonymously - but I don't know how to achieve that concretely.

[ericblade]

so you can't query if an activity exists unless you spoof, or are the creator?

[Tofee]

It seems so - it could be I missed something, too. Note that querying by activityId works well, if needed...
I guess they introduced the creator (and the kind, service or app) so that it's more unlikely to have name collision.

[ericblade]

ok, well, i guess it's not a bug then necessarily, perhaps a documentation flaw