On Tue, Jul 3, 2012 at 11:41 AM, brandall <[email protected]> wrote: > Thanks for your response Mark. The rest of the stack trace is: > > java.lang.IllegalArgumentException: contentIntent required: > pkg=com.brandall.nutter id=1079820303 > notification=Notification(vibrate=null,sound=null,defaults=0x0,flags=0x60) > > There's nothing else relevant in the output.
Is that in your null Intent case? The message makes more sense for that than with the TTS_SETTINGS scenario. It looks like contentIntent used to be required, but no longer is, as of October 2010 (in terms of source code updates). Do you see a pattern in OS versions in the devices that are hitting this? I would recommend using an Intent that points to one of your activities -- that avoids the TTS_SETTINGS problem and avoids the null contentIntent. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _The Busy Coder's Guide to Android Development_ Version 3.7 Available! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
