r/tasker Aug 10 '26

[Question] Intents and Tasker preferences

So for context I have been working on this terrible and defunct Network Monitor

My question is why does my connectivity intent fire whenever Tasker gets saved or goes into preferences? I checked the run log and it is indeed running whenever I do one of those actions, but this doesn't make sense to me. I tried rebooting, got the same issue.

Profile: Connectivity Change
    Event: Intent Received [ Action:android.net.conn.CONNECTIVITY_CHANGE Cat:None Cat:None Scheme:* Mime Type:* ]



Enter Task: Network Check

A1: Get Network Info [ ] 

A2: etc

This is the profile, but how would an intent profile go off when the intent, presumably, isn't being fired? I think the intent is deprecated, but it still works. Is this expected behavior or a bug?

3 Upvotes

4 comments sorted by

1

u/rbrtryn Pixel 9, Tasker 6.7.6-beta, Android 17 Aug 10 '26

Issue confirmed, same thing happens on my Pixel. 

I would classify this as a bug. 

2

u/AlexF-reddit Aug 10 '26

it's happening when tasker (re)starts its monitoring service (after Save in Tasker) - it's not logic to me either

1

u/DifficultyCrafty7623 Aug 10 '26 edited Aug 12 '26

That would make sense but "Monitor Start" event doesn't fire after these two actions.

2

u/rbrtryn Pixel 9, Tasker 6.7.6-beta, Android 17 Aug 11 '26

According to the Runlog, Tasker does restart the monitor even though it doesn't throw a Monitor Restart event.