No, I did not. Should I? There are currently no flags on the intent.
On Wednesday, July 18, 2012 10:33:46 PM UTC-4, Dianne Hackborn wrote:
Did you use PendingIntent.FLAG_CANCEL_CURRENT?
On Wed, Jul 18, 2012 at 7:55 AM, Matt Schoen mtsch...@gmail.com wrote:
Hi there,
I'm having an issue
The root of the issue is described here:
http://developer.android.com/reference/android/app/PendingIntent.html
If the creating application later re-retrieves the same kind of
PendingIntent (same operation, same Intent action, data, categories, and
components, and same flags), it will receive a
Thanks for the help! I actually ran with the previous response and chose
FLAG_CANCEL_CURRENT. Worked like a charm :)
On Thursday, July 19, 2012 9:45:12 AM UTC-4, Kostya Vasilyev wrote:
The root of the issue is described here:
Hi there,
I'm having an issue with an activity, which is started via a notification,
which is spawned by an alarm.
I've added debug outputs to determine whether the right data is being sent,
and it is. What's happening is this:
The alarm fires, which picks a random entry from my database,
Did you use PendingIntent.FLAG_CANCEL_CURRENT?
On Wed, Jul 18, 2012 at 7:55 AM, Matt Schoen mtsch...@gmail.com wrote:
Hi there,
I'm having an issue with an activity, which is started via a notification,
which is spawned by an alarm.
I've added debug outputs to determine whether the right
5 matches
Mail list logo
