AutoRemote Unintended Recursive Call

Discussion in 'AutoApps' started by Sudipta, Aug 18, 2015.

  1. Sudipta

    Sudipta New Member

    Joined:
    Aug 16, 2015
    Messages:
    3
    Likes Received:
    0
    Hello

    This is the scenario:
    I have 2 regex events setup in tasker

    1. call.*
    2. text.*

    The tasker tasks are
    1. call %arcomm using autoremote message syntax call=:=1234567890
    2. send text %arcomm to %arpar1 number using autoremote message syntax text 1234567890=:=Test Message

    Interesting reproducible behavior:

    When the text message contains the word "call", the first event gets fired as well.
    e.g. text 1234567890=:=Test Call Message

    This causes unintended dialing of a garbage no (actually not garbage but number representation of the text) besides the text being sent.

    Please let me know if you need any further details.

    Thanks,
    Sudipta.
     
  2. joaomgcd

    joaomgcd Administrator Staff Member

    Joined:
    Feb 3, 2015
    Messages:
    9,476
    Likes Received:
    797
    Set command filters to "call=:=" and "text=:=" :)
     
  3. Sudipta

    Sudipta New Member

    Joined:
    Aug 16, 2015
    Messages:
    3
    Likes Received:
    0
    Thanks a lot... This workaround solved the problem... didn't realize that message filtering does't understand the significance of =:= :)

    However this workaround is working because the syntax of "call=:=". This workaround will not work for the below scenarios:

    1. "call 0123456789=:=some text bla bla"
    2. "text 9009009000=:=need to call bla bla"

    Thanks,
    Sudipta.
     
  4. joaomgcd

    joaomgcd Administrator Staff Member

    Joined:
    Feb 3, 2015
    Messages:
    9,476
    Likes Received:
    797
    ok, then use "call.*=:=" and "text.*=:=" :)
     
    KaszasM likes this.
: recursive

Share This Page