When adding multiple actions to launch with one touch via the app method (no scripting), I noticed that it launches…
When adding multiple actions to launch with one touch via the app method (no scripting), I noticed that it launches one action at a time which I’m fine with it.
My problem is that I if I have a #Tasker action running before another action, and Tasker is disabled, the second action never runs.
Is there a way to bypass this, by identifying if #Tasker is enabled, and then skipping the #Tasker action if not enabled?
#llx #tasker #launch #actions
« Hey! New user here (actually very old, but restarted using it.) (Previous Post)
(Next Post) Interesting (minor-ish) issue I’ve encountered. »
D5 Creation
I’m not really sure to understand the issue sorry.
Even if tasker is disabled the second action will run, unless it is somehow related with the previous one.
Could you give more details about what you want to achieve?
Answering your question: no, there is no current way to enable/disable actions on the fly, the intended way is to use a script.
I’m using a #Tasker shortcut to open the play store in my apps section, and I have the default launch action after the #Tasker action which launches play store
my main intention is for it to work as a backup if #Tasker is disabled, so it can launch the store and then I can navigate wherever I have to go
but when I disable #Tasker nothing happens when I click the icon, not even the default action of the shortcut that is not #Tasker related gets launched
It is strange that the second action doesn’t work. But it should also run even if the tasker one runs correctly, so I think it isn’t correctly set or something.
As I said, you can’t enable/disable programmatically.
But, what you want to achieve (open play store on myapps) can simply be done with this small script. No tasker needed!
var intent = new Intent(“com.google.android.finsky.VIEW_MY_DOWNLOADS”);
intent.setClassName(“com.android.vending“, “com.google.android.finsky.activities.MainActivity“);
getActiveScreen().getContext().startActivity(intent);
when #Tasker is enabled, both actions gets launched no problem
My guess was that the first action got stuck waiting for a Tasker response or ended in a error and therefore the other action does not run
I know.. I’m kind of being lazy.. eventually I want to do more scripting because of the responsiveness is so fast, but I’ll give it a try
thanks for the script!
ตัวใครอยู่กลางโรงเรียนวิทยาลัยเทคนิคอุเทนถวาย ครับ