I'm probably going to make up terminology a little bit here.
Does the Intent Received event get triggered when an intent is broadcast in general, or only when the intent is sent directly to Tasker?
I'm trying to create a profile that will capture an intent (potentially sent by any application), manipulate it a bit, and resend it to whomever is listening. I have a particularly annoying app that rewrites its URLs to first hit its own site to count the click, then redirect to the actual URL. This causes the browser to open when it wouldn't need to in some cases, e.g. a YouTube link, since YouTube is listening for URL intents that match youtube.com.Also, what are some ways I can test Intent Received? I've tried creating a profile that listens for Intent Received (no action specified), and then alerts %intent_data
, but I can't seem to invoke it. I've tried clicking links within apps, sharing from one app to another, etc... nothing seems to trigger this profile. I've even tried adding an action to launch an app, just in case I was simply missing the message, but no avail.
Is it common for apps to use broadcast receiver? I read a bit about it in the Android docs and it seems like it's sort of discouraged, as other methods would be easier.
Is there an easier way than decompiling the app to tell the type and data set in the intent?
Is it common for apps to use broadcast receiver?
There is no way for a BroadcastReceiver to see or capture Intents used with startActivity(); likewise, when you broadcast an Intent, you will never find or start an Activity. These two operations are semantically very different: starting an Activity with an Intent is a foreground operation that modifies what the user is currently interacting with; broadcasting an Intent is a background operation that the user is not normally aware of.