Pending intent android studio code#

Broadcasts will make a bit more sense once we cover broadcast receivers, but for now think of them as sending a message to the system, in the form of an intent, and any component listening for that message can respond.

The other type of pending intent, broadcast intents, allows other apps to send a broadcast message on behalf of your app as if a context from within your app called sendBroadcast(). PendingIntent.getActivity(this, REQUEST_NOTIFY_LAUNCH, intent, 0) Intent intent = new Intent(this, MainActivity.class) NotificationCompat.Builder builder = new NotificationCompat.Builder(this) private static final int REQUEST_NOTIFY_LAUNCH = 0x02001 An example of what this looks like can be seen below.

Pending intent android studio code#

To call getActivity(), you must pass in a context, an optional request code to identify where the intent came from, the intent that you want the other app to launch, and some optional flags. To create an activity pending intent, you'd use the static getActivity() method of the PendingIntent class. This is also the type of pending intent that we'll use to set the default actions of a notification. This is helpful if you want a notification or other system component to be able to start an activity defined in your app. Activity pending intents allow the receiving app to start an activity from your app as if you called startActivity() from within your own app. There are two types of pending intents that you'll be using throughout this class and most of your Android development, activity and broadcast. Then, the notification can use that pending intent and launch your main activity as if the intent was launched from within your app. Then, you'd wrap that intent inside of a pending intent, and set it to be the action on the notification. Therefore, if you want your notification to launch your main activity, you'd setup an intent to launch that activity in very much the same way as you would any other intent. The only difference here is that pending intents allow other apps to launch intents using the same permissions and access rights as the app that created the pending intent. The intent that you place inside of a pending intent is exactly the same as any other intent that you'd create within your app. Instead, we need to use a PendingIntent.Ī pending intent is a holder for an intent and a target action. That means that your notification can't execute intents on behalf of your app just by giving it an intent since the launcher doesn't have the same access rights that your app does. However, while notifications are created by your app, they're not actually a part of your app, they're part of the Android launcher app. There will be times, however, when you want to hand off an intent to another app and allow that app to launch the intent on behalf of your app, with the permissions of your app.įor example, when your app creates a notification, you might want that notification to launch your app again when clicked. If you were to hand off that intent to another app and allow that app to launch that same intent, it would be launched with the permissions and access rights of the other app.

When firing off an intent in your app, that intent is launched with all of the same permissions and access rights as your app. To do this, you would need to give the other app a PendingIntent. At times, you'll need need to allow other applications to perform actions on behalf of your app.