0

I want to pass extras with my pending intent when I set an alarm to be picked up by my receiver in onReceive and then passed on as extras in my receive intent to be picked up by my scheduling service to be included in my notification.

E.g. set an alarm to remind me to take a medicine with name 'x' in 'y' amount of time. I want the name 'x' to be displayed in the notification when the alarm is fired.

I found this answer very helpful.

However, in the Google Android sample project scheduler available from here, it advises that if your receiver intent includes extras that need to be passed along to the service, use setComponent() to indicate that the service should handle the receiver's intent:

ComponentName comp = new ComponentName(context.getPackageName(), 
           MyService.class.getName());

// This intent passed in this call will include the wake lock extra as well as
// the receiver intent contents.
startWakefulService(context, (intent.setComponent(comp)));

The answer I referenced does not do this.

Is it only required to use setComponent when the component from onReceive is a service and this is not required when the component is an activity?

Thanks, Sam.

Community
  • 1
  • 1
samleighton87
  • 559
  • 1
  • 5
  • 13

1 Answers1

0

However, in the Google Android sample project scheduler available from here, it advises that if your receiver intent includes extras that need to be passed along to the service, use setComponent() to indicate that the service should handle the receiver's intent:

Nothing related to this appears on the page that you linked to.

The answer I referenced does not do this.

Yes, it does. It sets the component via the Intent constructor.

Is it only required to use setComponent when the component from onReceive is a service and this is not required when the component is an activity?

Setting the component, whether via the constructor or setComponent(), is used to indicate that this is the component that should handle the operation, creating a so-called explicit Intent. If you do not set the component, then other criteria, like the action string and Uri, will be used to infer who should handle the operation (an implicit Intent).

Generally speaking, where possible, use explicit Intent objects, with components that do not have an <intent-filter>, for maximum security.

The use of explicit versus implicit Intent objects has nothing directly to do with whether the component in question is an activity, a service, or a receiver.

CommonsWare
  • 986,068
  • 189
  • 2,389
  • 2,491
  • Re nothing related to this appears on the page - it is in the sample project which you can download from the page. – samleighton87 Mar 01 '15 at 14:11
  • I think Google is implying that if you want to pass the same intent along to the next component rather than take it's extras and make a new explicit intent you can reset the first intent's component so it is directed to your service. Thanks for your answer it helped me work this out. – samleighton87 Mar 01 '15 at 14:50
  • 1
    @samleighton87: "you can reset the first intent's component so it is directed to your service" -- that's certainly a possibility. This also allows you to effectively "convert" an `Intent` from one role to another. For example, with GCM, you get an `Intent` containing your message via a broadcast. However, often times you want to process that message in a `Service`, as the work involves disk or network I/O. Calling `setComponent()` to identify your service, then calling `startService()` with that `Intent`, will pass the `Intent` along to the service, with extras and such intact. – CommonsWare Mar 01 '15 at 14:58