It's not (easily) possible to determine which intents an app listensįor dynamically (i.e.
Using the aapt tool that comes with the Android SDK like this:Īapt dump xmltree example.apk AndroidManifest.xml Many intents that an app listens for are declared in its package manifest The type of Android component which should receive the intent. bunchofvalues:mybundle (where mybundle is the name of a Java object of type Bundle)Īllow specification of a particular package and/or class within the package to.If none of the above apply, the value will be treated as a String. The name of a Java object created via the Java Function action which is of type Parcelable can also be used (e.g. The value can also be forced to a simple type (long etc) or Uri via casting. If the value can be parsed as an integer, long (integer ending in L), floating point number, double (float ending in D) or boolean (true/false) it will be treated as one. The extras must be in the form of a single colon-separated key and value. The main data specification in the form of a URI.Ĭan't be used together with a Mime-Type specification.Īny additional data to send with the intent. Gives additional information about the action.įrom the developer reference: "This is used to create intents that only specify a type and not data, for example to indicate the type of data to return."Ĭan't be used together with a Data specification. What the sender would like the receiver to do with the data.
Note that any parameter specified except Extras will reduce the set of possible receivers You to provoke behaviour in other apps, when you know the particular form of intent they Tasker allows you to send arbitraty intents using the Send Intent action in the You can find information about intents and details of several built-in Android intents on the Android SDK
This document is not intended to explain how intents work, but Intents are Android's main method for allowing apps to communicate with each other and share data.
0 kommentar(er)
