Bug? Tasker does not apply settings.

[Niki]

Hi,

As mentioned in https://groups.google.com/forum/#!topic/tasker/mfHwnvakdaM, I have the problem (bug?) that Tasker sometimes does not apply settings, such as changes to profiles, tasks or enable/disable profiles.

This "bug" would explain a lot of "strange" bugs and behavior I was facing the last time such that Tasker did completely different things I was expecting or not reacting to certain events at all (such as the light sensor or USB connected).

The one way it seems I can resolve the problem is:

1. Disable Tasker
2. Exit tasker and turn off phone
3. Turn on phone
4. Enable Tasker again

When I only enable/disable Tasker (without exiting the app) something weird happens too: Tasker claims it is enabled (it's orange) but the notification icon does not appear until I exit tasker.

It's not so easy to reproduce because it happens only "sometimes". But if it appears it is easy to reproduce: Create a profile with Context "Light 0, 10" or "Power Connected USB". Although you mask the sensor or plug the phone to your computer (and connection works!) there is not a single line in the run log. It's also not just a delay - this is persistent - for seconds or minutes.

What's going wrong here and can it be fixed?

Thanks
Niki

[Rich D]

> What's going wrong here and can it be fixed?

Tasker needs to be fully exited ( via back button) for changes to be saved. This includes starting and stopping Tasker via the Tasker logo in upper left.

Some changes to actions can be run without saving out but when in question, save all the way out..

[Niki]

Thanks Rich.
Are you sure this is normal behavior? Do you also face it?
I used Tasker already 2/3 years ago with my HTC Desire and I can't remember having had such problems any time.
Also I wonder why this is nowhere documented.
In the end it makes the work really hard because Disable/Exit/Start/Enable/Exit/Start after every small change is cumbersome ;-)

Niki

[Rich D]

> Are you sure this is normal behavior?

Yes

Do you also face it?

Yup,
I saw pent mention he might implement some sort of 'Save' option within tasker, which would be very handy, not sure it is on the short list though..

> Also I wonder why this is nowhere documented.

There are a lot of undocumented things in Tasker, you can usually find most answers with a search of the group or of course ask here. I believe Pent being a one man show finds his time more valuable implementing new features and supporting the existing ones then trying to document every thing, I would agree.. besides if every little thing was documented it might take longer to find it in the docs then just doing a search or asking here..

> In the end it makes the work really hard because Disable/Exit/Start/Enable/Exit/Start after every small change is cumbersome ;-)
>

I agree that it is a bit of a PIA to exit then restart for changes while building and testing within tasker however I do not understand why you need to " Disable/Exit/Start/Enable/Exit/Start after every small change" as I stated when editing a task and actions I usually do not need to exit to test, and when I do I simply exit via back button then restart, there is no need to disable/enable.

Rich..

[Scott]

If it helps, I also find it best to deactivate, reactivate, save and exit to make sure my changes are saved.  It seems to happen more with plug-ins and any time I actually do something right.  Accidental changes to tasks are usually saved without hassle.

[Rich D]

> If it helps, I also find it best to deactivate, reactivate, save and exit to make sure my changes are saved.  

Hmmm, I have never had a problem simply exiting and re-entering...

[Scott]

I've had one or two times where some plug ins (the AutoApps seem to be the worst) didn't take on me just saving and exiting.  I tried deactivating and reactivating and then saving and exiting and that worked, so I've just stuck with it.  It probably isn't necessary for 95% of the changes I make.

[Pent]

> If it helps, I also find it best to deactivate, reactivate, save and exit to make sure my changes are saved.  

Hmmm, I have never had a problem simply exiting and re-entering...

Me neither.

You only need to exit to test tasks if you've changed something the task refers to e.g. another task or a scene.

Pent

[Niki]

Thanks, that's good to know!

I am also using exit & reenter now whenever I change something.
Seems to work.
Would still be cool to add this comment somewhere in the docu.