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.
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. ;)
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.
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)