Unsupported local error

[Jim A]

I started getting an error the past week that says "TTS unsupported local:default:default"  anytime a tasker script references either GPS or Cell tower location (I don't know which exactly since my script references both, GPS first and if it times out then cell tower).   Once that error is fired it appears to generate an 'un caught exception' (in java speak) and the script is done.   I haven't installed any new software (at least that I am aware of) that would affect GPS or cell tower locations.   Any guess what might be happening here?  Ok, then here's my guess, the GPS request is returning some error to tasker and tasker is just passing it along by firing an exception that isn't caught until its all the way at the top and already out of any profile execution.

One thing I do wish that Tasker would do is let me decide (i.e. the task that I write) what to do with an error rather than deciding for me.   I have several tasks that if I had control I would programatically say "I don't know what this error means ether but I don't care because killing the loop in the task is worse than just plowing ahead and ignoring the error"   Pent, have I missed a way to do that already or would you consider putting that on a 'to do' list?

[Matt R]

"TTS" suggests it's related to the text to speech engine.  Are you using a say command in that task?  If so, try setting a specific voice engine in that action (with the magnifying glass).  Also, many actions, including say and get location, have a "continue task after error" option at the bottom, which I think is what you're requesting.

Matt

[Jim Amen]

>TTS

 

Ahh… the three letter acronym game.  Usually I’m pretty good at guessing those but I missed this one.  Thanks.

 

> Are you using a say command in that task? 

 

Yes.  Just found that in another thread a few minutes ago.  Switched it from Ivona to Google and it seems to work.   Google’s female voice is really annoying however.

 

> Also, many actions, including say and get location, have a "continue task after error" option at the bottom, which I think is what you're requesting.

Yes I’ve tried that and as best I can tell I have everything set to continue task after error.   It doesn’t seem to make any difference though which is why I think the exception that is originally thrown isn’t of a class type that is caught by that check box.

--
You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/pWtUGoy04O8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tasker+un...@googlegroups.com.
Visit this group at http://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/groups/opt_out.

[Pent]

I can't find the error you mention in the code.

Perhaps you are using an old Tasker version ?

Pent

[Jim Amen]

Thanks for the reply Pent,

Some one else suggested it was text to speech, and they were right.  My scripts use gps to tell me things so it was always doing both gps and tts.  I assumed locale=gps but was wrong.   I switched from your old friend Ivona (I searched the other threads then :) ) and found you had had trouble with her before.  (googles voice is awful to listen to though)

I'd still like to see some other exception handling options though.  I always check the 'continue on error' check box whenever I find one but my experience is that exceptions toss me out of the loop and then I'm dead, like this example.  The text to speech fired an exception that's clear now, but it  didn't seem to be caught by tasker until very high and out of my control. 

Sent from Jim's iPad

[Pent]

I'd still like to see some other exception handling options though.  I always check the 'continue on error' check box whenever I find one but my experience is that exceptions toss me out of the loop and then I'm dead, like this example.  The text to speech fired an exception that's clear now, but it  didn't seem to be caught by tasker until very high and out of my control. 

The Say action has a continue on error parameter. If the task is stopping at that point (please check Menu / More / Run Log) then
an unexpected exception is happening somewhere that we can try to find. As I said, I can't find the error you reported in the code,
are you sure that's the literal text ?

Also, if you have particular actions for which Continue On Error would be useful, please mention. It was added at a late stage, and so I've only applied it to actions for which users have asked for it till now.

Pent

[Jim Amen]

I have the "continue on error" checked for the say command.  I don't see an abend in the run log but when I open tasker I get a list of errors ( all the same).  Ther is a set of three numbers that precede the text in this list that but I don't know what they mean.  The text is "correct" but may not be formatted exactly the same since it wasn't easy to cut and paste.   I don't think tasker is generating the error which is why you can't find it.  I think the text to speech is passing a string that gets in one or the other log.  Again, I don't see (maybe I'm blind to it) the error message in the run log but I see it when I open tasker GUI.  Getting rid of Ivona solved it.   Maybe what's being fired for an error is something higher than the run level that tasker is executing, like an os error or something.   I think you would have better luck finding the string in the source of Ivona than in the source of tasker.

Still think it might be nice to be able to declare a sub task ( like calling a sub routine) at the beginning of a task that will process errors.

Sent from Jim's iPad

--

[CazMaz]

Hi Jim,

Try to use logcat, it's free from the play store.
I use it to see the system log and it helps me to see the behind the scenes activities step by step, including what android and other apps are doing. I would bet that the error for this would be logged there, too.
It also let's you copy and paste into a text editor or email.

Cazmaz