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. That is returned in all cases...null or activity. 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. It's definitely replicated when using the main activity to launch the application. The stack did also contain: W/19:27:15.560 ActivityManager( 220)

Solutions on the web34833

  • via Google Groups by brandall, 5 months ago
    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. It's definitely replicated when using the main activity to launch the application. The stack did also contain: W/19:27:15.560 ActivityManager( 220)
  • contentIntent required: pkg=com.rootsoft.standout id=721391847 notification=Notification(vibrate=null,sound=null,defaults=0x0,flags=0x60)
  • via Stack Overflow by user4583520
    , 1 year ago
    contentIntent required: pkg=com.android.saathi id=1 notification=Notification(vibrate=null,sound=null,defaults=0x0,flags=0x0)
  • Stack trace

    • 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. That is returned in all cases...null or activity. 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. It's definitely replicated when using the main activity to launch the application. The stack did also contain: W/19:27:15.560 ActivityManager( 220) at com.android.server.NotificationManagerService.enqueueNotificationInternal(NotificationManagerService.java:888)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You are the first who have seen this exception. Write a tip to help other users and build your expert profile.