Touch action not consistent when launching shortcut and app

Hello,

This is happening with a touch action inside a root or nested element that launches both a shortcut and an app.

The shortcut (automate flow shortcut that plays a sound file) is always executed, however the app launch is sporatic.

Usually if I tap the element a second time, the app is launched.

If it will help, I can provide a code example and a debug log.

Thanks!

-josh

I have tested this and i cannot reproduce the issue on 3.23, can you confirm you are launching activities from different apps? Also please ensure you are at least on 3.22 since i changed the way touch works a lot from previous release.

Hi Frank... thanks for the reply.

Well I was on 3.22, but just upgraded to the 3.23 beta and am having no issues at all!

Some touch elements had both a direct launch app and a "shortcut", and others had "activities" and a "shortcut". I was seeing the same behaviour in both situations.

But whatever you changed between 3.22 and 3.23, you fixed it. ;)

Thanks again Frank!

-josh

I am on 3.25b715214, and am still having this issue. Specifically, trying to use both "Launch App" and "Launch Shortcut" (to launch a Tasker shortcut) causes a conflict, and it doesn't seem to want to do both. It seems to be related, at least for me, to the order of the touch action, but I can't confirm that, as it doesn't always work, no matter the order.

Thanks for the reply David.

I've found this issue goes away if you clear klwp cache and/or reload the wallpaper, but it does come back eventually.

Very annoying bug.

Will clearing the cache mess up my setup? I don't have pro (yet), so I can't save my present :(

Its usually not possible to execute 2 intents at the same time, i should even deny that from the app itself, i will investigate this further but there might be no solution to this (i mean you can toggle globals and other stuff, but Android Intents like shortcuts and app launches might not be parallelized)

Its usually not possible to execute 2 intents at the same time, i should even deny that from the app itself, i will investigate this further but there might be no solution to this (i mean you can toggle globals and other stuff, but Android Intents like shortcuts and app launches might not be parallelized)