1

Tasker sometimes returns/detects a zero as caller id

A few months ago i was having trouble with a profile that sends an SMS prompting an unknown (not in address book) contact to identify itself. The profile sometimes stopped sending the SMS so i added a second text file that logs every caller id regardless. Since then everything seemed to work fine until a few days ago when the app, once again, did not send the SMS as instructed. It turns out that tasker detects a zero as a caller id when in fact it is plainly visible in the call logs. Is this a known bug?

------------------------------------------

Profile: 1-Unknown Caller (2)
Cooldown: 300
Event: Missed Call [ Caller:!C:ANY ]
Enter: Sconosciuto (3)
A1: Write File [ File:/storage/2B7C-6A21/Download/tutti.txt Text:%CNUM Append:On Add Newline:On Continue Task After Error:On ]
A2: If [ %CNUM ~ +393* ]
A3: Write File [ File:/storage/2B7C-6A21/Download/sconosciuti.txt Text:%CNUM Append:On Add Newline:On Continue Task After Error:On ]
A4: Send SMS [ Number:%CNUM Message:Text Store In Messaging App:On SIM Card: Wait For Result:Off ]

Follow

2 replies

Votes Newest Oldest

Hi. Does Tasker maybe not have the Call Log permission granted?

Comment
AP

Hi. Yes, i've just checked Tasker permissions and everything is enabled. GPS call log etc.

What i tried just today was to run an action and %CNUM kept giving me back 0 even though the last number alled was a regular mobile number. I've uninstalled and reinstalled tasker, let the phone ring again and now %CNUM showed the correct number and not a zero. It seems that at one point the variable turns into a constant with a 0 forever.

AP

Hi. Yes, i've just checked Tasker permissions and everything is enabled. GPS call log etc.

Comment
Reply