Take the 2-minute tour ×

Hey Guys, I am having a problem with the alarmManager and the pending intent with extras that will go along with it. If I set multiple alarms, They will go off however the extras stay the same. I have already read into these questions ( android pending intent notification problem and Android keeps caching my intents Extras, how to declare a pending intent that keeps fresh extras? ) and tried assigning a unique id to each pending intent and have tried using all the pending intent flags to no avail. I have no clue why it will not work. Here is a code snippet:

Intent intent = new Intent(con,
            intent.putExtra("foo", bar.toString());

            int id = randomNum;

            PendingIntent sender = PendingIntent.getBroadcast(con, id,
                    intent, PendingIntent.FLAG_UPDATE_CURRENT);

            AlarmManager am = (AlarmManager) con.getSystemService(Context.ALARM_SERVICE);
            am.set(AlarmManager.RTC_WAKEUP, scheduleExecution, sender);
share|improve this question
add comment

3 Answers

up vote 29 down vote accepted

Possibly two different issues here:

1) If you've already created your PendingIntent before and it "matches" an existing PendingIntent, then you must specify the PendingIntent.FLAG_UPDATE_CURRENT flag or it will not pass the extras. A "match" is based on the criteria that Intent.filterEquals() uses, so definitely read the docs there and make sure you understand the data, action, type, etc.

2) I've read that if you do NOT set an action on your intent, then it will not propagate the extras, so perhaps try intent.setAction("com.blah.Action").

share|improve this answer
In my pending intent I try to set the PendingIntent.FLAG_UPDATE_CURRENT, but now when the intent is called, I get an error like "java.lang.IllegalArgumentException: Can't use FLAG_RECEIVER_BOOT_UPGRADE here" - no idea though where this BOOT flag is coming from, all I added wa the FLAG_UPDATE_CURRENT. Did you have similar issue before? (I'm on Huawei Ideos, 2.2) –  Mathias Lin May 8 '11 at 3:55
Setting an action indeed solved my problem, thanks! –  shawkinaw Jun 13 '12 at 21:40
setaction was good for me .. same problem –  catalin87 Feb 10 '13 at 0:17
PendingIntent.FLAG_UPDATE_CURRENT worked for snooze and dismiss buttons!!! –  Mailis Toompuu Dec 23 '13 at 14:11
add comment

This could be due to Activity::getIntent returning the Activity's original intent given certain intent flags/filters.

If that is the case for you, you'll need to look at Activity::onNewIntent. Override that method, and the intent passed to that function should be the new intent with proper extras, etc.

Credit goes to this SO question that helped me to solve my problem: Why is my searchable activity's Intent.getAction() null?

share|improve this answer
add comment

I've run into a similar problem. Using PendingIntent.FLAG_ONE_SHOT may solve the problem, because it means the PendingActivity won't be reused.

share|improve this answer
add comment

Your Answer


