Anything like tasker://assistantactions or tasker://secondary in Kid Apps?

[whitedavidp]

I have found these to be a good way to link other apps to Tasker. Are these or something like them carried over into Kid apps made with AppFactory?

Thanks

[whitedavidp]

On a related topic, can shortcuts to tasks in kid apps be possible? In 2012, Pent seems to have said no.

I suspect and understand that kid apps are a rather unique thing and bound to be limited compared to Tasker itself. But once you get hooked on these utility abilities, it is hard to live without them.

Thanks

[João Dias]

Unfortunately not supported at the moment, sorry!

Thank you for your contact.

   Join: connect multiple devices (send pushes, remote SMS, notifications) on Android, Windows, Mac, Linux

   Tasker: customize/automate anything on your phone!

   AutoApps: add advanced functionality to Tasker via plugins

     

João Dias

[whitedavidp]

Thanks. I suspected as much.

If I specify the kid app's package name when broadcasting the net.dinglisch.android.tasker.ACTION_TASK intent, will this get picked up in the kid app? My initial testing of this says NO. But I thought I should check. Thanks.

[whitedavidp]

I just discovered that %launch_data is sent to the kid app upon startup. That could provide what I need for the time being. Tasker is amazing!

Sadly, I cannot seem to trigger the activity to start via the Chrome Intent mechanism. I am using:

intent://#Intent;action=net.dinglisch.android.taskerm.Kid;package=my.kid.app.package.name;S.myextra=mystring;end

hoping that the myextra=mystring gets put into %launch_data in a form I can use.

However, the kid app is not being launched. I am not sure, but the Chrome docs say that for this to work, the activity must declare android.intent.category.BROWSABLE in its category filter. When I look at the manifest in the kid app, I only see the following for this activity:

<intent-filter>
                                <action android:name="android.intent.action.MAIN" />
                                <category android:name="android.intent.category.LAUNCHER" />
 </intent-filter>

I am interesting in this so I can fire tasks in the kid app from other apps - especially Kustom Live Wall Paper when one of their UI elements are touched. I would guess this could be useful in other places as well.

Thanks.

[whitedavidp]

It seems that my intent info was not right. Using:

intent://#Intent;component=my.kid.app.package.name/net.dinglisch.android.taskerm.Kid;S.myextra=mystring;end

I get the kid app to launch. So perhaps the category filter is not at issue at all.

I am finding, however, that no matter what I specify for extras (using the specs shown here), the value of %launch_data is always shown as //. I have no idea if this is an issue in Tasker or in the Chrome stuff (or, as always, me).

[whitedavidp]

This may actually end up working.

First problem is ME (of course): %launch_data is not for extras. I guess there is no way to get any provided extras into the kid app. At least I cannot find that.

Next is not fully appreciating the format of the intent:// which I find more fully discussed here. I have found that if I use something like this:

intent://datahere/#Intent;component=my.kid.app.package.name/net.dinglisch.android.taskerm.Kid;end

I get something including the datahere in %launch_data.

I also find similar if I use something like this:

intent://#Intent;scheme=datahere;component=my.kid.app.package.name/net.dinglisch.android.taskerm.Kid;end

I am not claiming that I fully understand all this. But it seems possible now for me to use this mechanism to launch tasks within a kid app (or pass in some other data) using this mechanism.

Wow!

[João Dias]

Wow, nice 😅 Very glad you figured all that out!!