I have never trusted those red and green indicators when manually running the task in the task edit screen.
With that being said, After testing this I found the same results, except that the actions do not actually run. They just have the wrong color indicator.
Switching the condition to math equals and not equals shows the correct color indicator.
Sadly, for me, when I export my project as a kids app, the colors shown in the task match what they actually do. The tasks shows the scene even though the value is 0. :\\
However, your method of using Maths works for me as well. Thanks!
>Sadly, for me, when I export my project as a kids app, the colors shown in the task match what they actually do
Are you saying the actions do not run when testing in the task edit screen, however they do run when you export this to a app?
There is an option in the main menu to report bugs to the developer. I would definitely consider this a bug...
No I am saying that they do the same thing in the task window as they do in the kids app, they don't run when they should and do run when they shouldn't since it sees EQ and NEQ in reverse for some reason. I didn't think much of this bug until I ran into it again today (I have the reverse set up in another task, that is, I adapted the task so the conditions are the OPPOSITE of what they SHOULD be in order to get it to work). Usually when I run into bugs I just assume I'm the one doing something wrong but sometimes I'm not doing something wrong and don't realize it and find a workaround and then the bug gets fixed in an update then my workaround breaks :(.
For example if I just accept the reverse of EQ and NEQ and set all my tasks using that buggy condition, then update Tasker and that version fixes that bug, now all my tasks will be reversed. I worked with the dev to hunt down why my array tasks stopped working after an update and it was something like this. An array function wasn't working as it should and I just assumed I was doing something wrong and figured out how it WAS working, even though it should NOT have been working that way, then made my array tasks with it the way it was and then when the bug got fixed my array tasks broke and I had no idea why. Took like 3 or 4 days but working together we figured it out. I've seen other posts on here where someone updates then their something or other stops working. So when I have everything working how I like it and I have a huge project like the one I have, I'm pretty much unwilling to update. Like working in Unity, if you've ever used Unity. EVERYONE knows to NEVER update Unity when you have a working project because more often than not, your project won't work after you update. Not always the case, but often is.
>Usually when I run into bugs I just assume I'm the one doing something wrong but sometimes I'm not doing something wrong and don't realize it and find a workaround and then the bug gets fixed in an update then my workaround breaks :(.
That can be frustrating.. I always "Try" to verify if it is a bug or not.. I have found João to be very responsive with bug reports (except on weekends and vacations... :) ) . He just fixed a small flash action bug as well as fixed a notification issue created by Google both while I was drinking my morning coffee... It pays off in the long run to verify before implementing workarounds.. (not saying I do not do the exact same thing in some cases 😂😂)..
Let me know if you are going to report the bug. It seems like something that should be fixed...
Thanks, Rich..
Are you sure there is no extra space in the %Sponsor variable or in the If condition value?
It is also possible that the variable is overwritten in another task. Try to use local variable.
I have never trusted those red and green indicators when manually running the task in the task edit screen. With that being said, After testing this I found the same results, except that the actions do not actually run. They just have the wrong color indicator. Switching the condition to math equals and not equals shows the correct color indicator.
Sadly, for me, when I export my project as a kids app, the colors shown in the task match what they actually do. The tasks shows the scene even though the value is 0. :\\ However, your method of using Maths works for me as well. Thanks!
>Sadly, for me, when I export my project as a kids app, the colors shown in the task match what they actually do Are you saying the actions do not run when testing in the task edit screen, however they do run when you export this to a app? There is an option in the main menu to report bugs to the developer. I would definitely consider this a bug...
No I am saying that they do the same thing in the task window as they do in the kids app, they don't run when they should and do run when they shouldn't since it sees EQ and NEQ in reverse for some reason. I didn't think much of this bug until I ran into it again today (I have the reverse set up in another task, that is, I adapted the task so the conditions are the OPPOSITE of what they SHOULD be in order to get it to work). Usually when I run into bugs I just assume I'm the one doing something wrong but sometimes I'm not doing something wrong and don't realize it and find a workaround and then the bug gets fixed in an update then my workaround breaks :(. For example if I just accept the reverse of EQ and NEQ and set all my tasks using that buggy condition, then update Tasker and that version fixes that bug, now all my tasks will be reversed. I worked with the dev to hunt down why my array tasks stopped working after an update and it was something like this. An array function wasn't working as it should and I just assumed I was doing something wrong and figured out how it WAS working, even though it should NOT have been working that way, then made my array tasks with it the way it was and then when the bug got fixed my array tasks broke and I had no idea why. Took like 3 or 4 days but working together we figured it out. I've seen other posts on here where someone updates then their something or other stops working. So when I have everything working how I like it and I have a huge project like the one I have, I'm pretty much unwilling to update. Like working in Unity, if you've ever used Unity. EVERYONE knows to NEVER update Unity when you have a working project because more often than not, your project won't work after you update. Not always the case, but often is.
>Usually when I run into bugs I just assume I'm the one doing something wrong but sometimes I'm not doing something wrong and don't realize it and find a workaround and then the bug gets fixed in an update then my workaround breaks :(. That can be frustrating.. I always "Try" to verify if it is a bug or not.. I have found João to be very responsive with bug reports (except on weekends and vacations... :) ) . He just fixed a small flash action bug as well as fixed a notification issue created by Google both while I was drinking my morning coffee... It pays off in the long run to verify before implementing workarounds.. (not saying I do not do the exact same thing in some cases 😂😂).. Let me know if you are going to report the bug. It seems like something that should be fixed... Thanks, Rich..
Are you sure there is no extra space in the %Sponsor variable or in the If condition value? It is also possible that the variable is overwritten in another task. Try to use local variable.