Forwarding SMS occurs twice

[Brandon Horwath]

Here is the profile:

Profile: Forward To Personnel (300)
Event: Received Text [ Type:Any Sender:Contact A/Contact B/etc... Content:* ]
Enter: Forward SMS (299)
A1: Send SMS [ Number:XXXXXXXXXX Message:%SMSRN at %SMSRF sent message: %SMSRB Store In Messaging App:On ]
A2: Flash [ Text:SMS Forwarded Long:Off ]
A3: Stop [ With Error:Off Task:Forward SMS ]

Now, this works. But, ALWAYS sends two forwarded messages.

Any ideas?

I have tried adding a semaphore, no luck. The log shows the task activating from this profile only, 2 seconds apart from each other. As though the context for activation occurs twice when a single SMS is received.

[Brandon Horwath]

Oh, and A2 only flashes once. So, the task only occurs once (abort new task enabled) but two messages are still sent.

[SunKol]

Do you have two SMS Apps installed.? Like Stock and GO SMS / HENDSENT. If yes, can you check keeping on stock active (rest disable completely). 

B'coz I feel both APPs must be saying " OK...I received a SMS" and Tasker is then acting on two notices. But, take This is just a hint.

Sunil.

[Bob Hansen]

Just a thought. 

Do you see a second received test event if you don't send the sms? 

[Brandon Horwath]

Sunil,

Nope. Only stock.

Bob,

Interesting. I hadn't thought of that. The event recognition usually occurred before the task completed sending any SMS, so I hadn't thought about that.

After testing, it does :-(

See: http://db.tt/eCAcOZ8a

I thought I would try a bombardment of tests, here are the results:

Received 1 message, sent 2 messages
Of those 2 messages, 1 received, 2 sent in reply
Of those 2 messages, 1 received, 2 sent in reply
Of those 2 messages, 2 received, 3 sent in reply
Of those 3 messages, 1 received, 1 sent in reply
Received 2 messages (carrier delay?), 1 message sent in reply
Received 2 messages (carrier probably hates me), 1 message sent in reply
Received 1 message, sent 4 (four!) messages?!?
Received 7 messages in response! Eek!

I stopped testing after that...!

[Bob Hansen]

So if the task collision is set to abort new task and you add a 1 second delay to the beginning of the task, then I would think that the second event would effectively be ignored. Right?

[Brandon Horwath]

So if the task collision is set to abort new task and you add a 1 second delay to the beginning of the task, then I would think that the second event would effectively be ignored. Right?

Uh, well... I could try it.

It just seemed weird it kept the task queued and did not reject the copy.

I will add that in and see.

[Brandon Horwath]

Added wait. No luck :-(

Still sends two.

[Bob Hansen]

This just might work!

This profile will not forward a text if a text was forwarded within the last 3 seconds. If I read the tea leaves right, this will get around the problem.

What do you think?

Profile: Forward To Personnel (300)
        Event: Received Text [ Type:Any Sender:Contact A/Contact B/etc... Content:* ]
Enter: Forward SMS (299)

        A:1  if %LastReplyTime > %TIMES - 3   <== last reply was less than 3 seconds ago

        A:2  Flash  Skipped

        A:3  Else

        A:4  Send SMS [ Number:XXXXXXXXXX Message:%SMSRN at %SMSRF sent message: %SMSRB Store In Messaging App:On ]

        A:5  Variable Set %LastReplyTime to %TIMES 

        A:6  Flash [ Text:SMS Forwarded Long:Off ] 

        A:7  End If

[SunKol]

Hi

I tested this creating exactly same profile. It sent just one.

Therefore I feel you should consider followings.

1. Delete task an profile. Root. Create same profile again and test

2. Check for any trace of another sms app may be deleted but some of it services may be there.

3. In Flash check the LONG.

4. Add a popup before sms send to know recipient nos.

5. Check for any duplication of event by some other profile. It happens we just have another profile sometimes and just ignored.

6. Can you try sending it to another no altogether.

Suniil

[Brandon Horwath]

Thanks Bob! I will have to try that!

Since my problem is the task doesn't get a reject copy unless I get two context activating SMS messages at the exact same moment, I think this might be a viable solution.

If the task was doubling and running simultaneously, this probably wouldn't work :-(

However, since the log shows (screenshot in link) that the task remains queued and runs after completion the first time, I am optimistic this will be a good solution :-)

Thanks again sir! I will play around with the idea and let you know!

[Brandon Horwath]

Hi

Hello :-)

I tested this creating exactly same profile. It sent just one.

The one I posted? Or Bob's suggestion?

Therefore I feel you should consider followings.

Open to suggestions... whatcha got?

1. Delete task an profile. Root. Create same profile again and test

Huh? Delete it, root my phone? Create it again and test? But, ummm... doing the same thing and expecting different results is by definition... never mind. I probably don't understand what you mean specifically.

2. Check for any trace of another sms app may be deleted but some of it services may be there.

... pretty sure nothing like that exists on my device. I keep everything stock on it when possible. My messaging app (normally) works just fine. I guarantee I know what my phone has and doesn't have on it. But, I understand for resolving this problem this is a necessary check. Thanks :-)

3. In Flash check the LONG.

Um, okay... I'll try that.

4. Add a popup before sms send to know recipient nos.

huh? To know recipient what? Why? What are you looking to have me isolate with this action?

5. Check for any duplication of event by some other profile. It happens we just have another profile sometimes and just ignored.

I'm sorry... what? I can see in the log what profile, task, and actions are activating. Also, I keep similar tasks group in projects and there are no duplicates. Is this what you were looking to have me check?

6. Can you try sending it to another no altogether.

In other words, does my messaging app send a duplicate when sending a SMS to a different device?

Yes, it does. But, ONLY when activating context is receiving another SMS. When composing or sending a SMS via manually controlled methods, i.e. my autovoice profile that will text my wife whatever I say when I begin the words with, "Hey honey," will only send one SMS.

Sending a SMS to my wife's phone from a SMS received context results in duplication again.

It's almost like my phone sends TWO intents or whatever tasker recognizes as an SMS received event. I believe, where most nearly all devices send one, mine happens to send two or two such "signals" tasker recognizes as an SMS received event.

I really can't think of anything else that would cause this specific issue.

Thanks for the suggestions Sunil, I had some questions though. Hope maybe you can clarify for me :-)

[Brandon Horwath]

This just might work!
This profile will not forward a text if a text was forwarded within the last 3 seconds. If I read the tea leaves right, this will get around the problem.
What do you think?

I think, that you sir are a genius.

I altered this a bit and played around with it. 3 seconds difference is just the right amount of wait time too.

It HAS to be two sent recognition contexts!

I get a flash, SMS Forwarded, followed by, Duplicate SMS Bypassed, which is what I happened to use in place of your suggestion.

Thank you immensely for your assistance with this Bob!

and for your efforts too Sunil.

[Bob Hansen]

Brandon

I am happy to hear that it worked! Got lucky with the 3 second wait. Picked 3 because I thought 2 probably would work, but wanted to be safe so added an extra second. Isn't it amazing what a little coffee will do;>?

[TomL]

I had posted this before in another thread, but I think it's amusing enough to repeat.

In case else anyone plans on creating a profile that sends two replies to every text message received, beware of the geometric sequence avalanche of texts generated if you should text yourself by accident.

Forget you have the auto-reply profile, send 1 text to yourself.

Receive 1 text from yourself, auto-reply back to self with 2.

Received 2 from auto-reply, auto-reply with 4. 

Get 4, reply with 8.

Get flooded with 8, retaliate with 16.

etc etc.

Assuming a leisurely pace of 3 seconds between send and auto-reply, after about a minute of this, you would have sent and received 1.5 million texts.

And what if your profile auto-replies with 3 texts?  

2.3 billion texts after a minute.

Have fun!

Tom

[Brandon Horwath]

Isn't it amazing what a little coffee will do;>?

Oh! Lol!

... well then I guess I owe you a case of your favorite blend ;-)