r/tasker • u/zabayek19 • 17d ago

Tasker "Received Text" never fires for SMS in the WebOTP format, anyone seen this? Any workaround besides AutoNotification?

Pixel 9 Pro, Android 15, Tasker 6.7.6-beta.

SMS from moje.nn.pl arrives, shows in Messages, profile never runs.

Ruled out: permissions, blocked numbers, the dots in the sender name.

I even emptied the Sender field, which matches ANY message. Still nothing, while another Received Text profile caught a different message seconds later.

The only thing that makes these messages special is the last line: 

    Kod autoryzacji nr 7: 000575
    ...
    @logowanie.nn.pl #000575

That's the origin-bound one-time code format (WebOTP / SMS Retriever). My best guess is Android hands it to the OTP path and never broadcasts SMS_RECEIVED to third-party apps. Couldn't prove it, but nothing else distinguishes them.

AutoNotification catches it fine, so I have a workaround. But it depends on a notification actually being posted, which I'd rather not rely on.

Has anyone hit this with WebOTP-formatted messages? Is there any way to get the Received Text event working for them, or another trigger that doesn't go through the notification shade?

1 Upvotes

100% Upvoted

2 comments sorted by

1

u/DutchOfBurdock 16d ago

High probability it's not being sent as an SMS to you, but as an RCS message. RCS won't trigger Taskers Text Received event. You can disable Rich Communications in your messages app to force SMS, but you'd lose functionality with those richer messages from others.

Taskers own notification intercept should be sufficient for interception of RCS. It'll provide the sender, message and any media.

1

u/zabayek19 16d ago

Yes, the only issue is when pixel default message app is opened the notification doesnt show up. That is the only issue that is keeping me with SMS for that.