An intent filter is an expression in an app’s manifest file that specifies the type of intents that the component would like to receive. When you create an implicit intent, the Android system finds the appropriate component to start by comparing the contents of the intent to the intent filters declared in the manifest file … Read more
You can’t do this directly, but you can create an activity alias in your AndroidManifest.xml with the intent filter in question, and then enable or disable the alias using PackageManager#setComponentEnabledSetting(), leaving your other intent filters in the main copy of the Activity so they won’t be affected.
I thought I will post this here since I spent some time looking into why my intent filter did not work. It turns out that it was working all along but matches are exact. Thus if you register your intent for http://myexample.com and you click in http://myexample.com/blah it will not work. Adding the following fixed … Read more
If you want your app to be started by your tag and want to receive the parsed NDEF message, your tag should contain the following: An NDEF record that you want to filter upon as the first record of the NDEF message (you can only create intent-filters for the very first NDEF record on an … Read more
You can share plain text with the following code String shareBody = “Here is the share content body”; Intent sharingIntent = new Intent(android.content.Intent.ACTION_SEND); sharingIntent.setType(“text/plain”); sharingIntent.putExtra(android.content.Intent.EXTRA_SUBJECT, “Subject Here”); sharingIntent.putExtra(android.content.Intent.EXTRA_TEXT, shareBody); startActivity(Intent.createChooser(sharingIntent, getResources().getString(R.string.share_using))); So your full code (your image + text) becomes private Uri imageUri; private Intent intent; imageUri = Uri.parse(“android.resource://” + getPackageName() + “/drawable/” + “ic_launcher”); … Read more
If your receiver is registered in the manifest, and your app is not running, a new process will be created to handle the broadcast. If you register it in code, it’s tied to the life of the activity/service you registered it in. For some broadcasts, it doesn’t really make sense to create a new app … Read more
For anyone else coming across this thread I had this issue and was pulling my hair out. I had the service declaration OUTSIDE of the ‘< application>’ end tag DUH! RIGHT: <manifest xmlns:android=”http://schemas.android.com/apk/res/android” …> … <application android:icon=”@drawable/icon” android:label=”@string/app_name”> <activity …> … </activity> <service android:name=”.Service”/> <receiver android:name=”.Receiver”> <intent-filter> … </intent-filter> </receiver> </application> <uses-permission android:name=”…” /> WRONG … Read more
If you want to diable processing of NFC discovery events (NDEF_DISCOVERED, TECH_DISCOVERED, TAG_DISCOVERED) while a certain activity is in the foreground, you would register that activity for the foreground dispatch system. That activity can then ignore these events (which it would receive in its onNewIntent() method. This will prevent NFC discovery events to be delivered … Read more
Categories are used for implicit Intents. So, If your Activity can be started by an implicit Intent when no other specific category is assigned to activity, activity’s Intent filter should include this category. (even if you have other categories in the Intent filter). If you are sure that your activity must be called with any … Read more
You need to set it up like this : <intent-filter> <action android:name=”android.intent.action.VIEW” /> <category android:name=”android.intent.category.DEFAULT” /> <category android:name=”android.intent.category.BROWSABLE” /> <data android:host=”example.com” android:pathPrefix=”/someresource/” android:scheme=”http” /> <data android:host=”www.example.com” android:pathPrefix=”/someresource/” android:scheme=”http” /> </intent-filter> Notice that in your case, you would need to use android:pathPrefix instead of android:path.