Bad Notification: Couldn't expand RemoteViews for: StatusBarNotification. on Android Nougat

[jpusp]

I'm receiving this issue on crashlytics only on Motorola devices with Android Nougat:

Fatal Exception: android.app.RemoteServiceException: Bad notification posted from package br.com.vivadecora.app: Couldn't expand RemoteViews for: StatusBarNotification(pkg=br.com.vivadecora.app user=UserHandle{0} id=1610499692 tag=null key=0|br.com.vivadecora.app|1610499692|null|10093: Notification(pri=0 contentView=null vibrate=null sound=null defaults=0x0 flags=0x218 color=0xffcd3128 groupKey=filter vis=PUBLIC))
       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1644)
       at android.os.Handler.dispatchMessage(Handler.java:102)
       at android.os.Looper.loop(Looper.java:154)
       at android.app.ActivityThread.main(ActivityThread.java:6123)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:867)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:757)

It works well on all other android versions and manufacturer. I dont have more information besides this log.

Thanks

[jkasten2]

@jpusp Can you share the OneSignal notification id that matches this crash with OneSignal support? You contact them via the OneSignal dashboard or by emailing support@onesignal.com

[jpusp]

I have one more information about this bug: It start to appear in crashlytics every time i release a new version to the Google Play. It appears that onesignal sdk crashes the app only one time, when the user updates the app. Then the app stabilizes

[anukools]

@jkasten2 I am also facing the same issue. And its behavior is same as mentioned by @jpusp that it crashes after few day of app updates then get stable.

[jkasten2]

@anukools Are you only seeing the issue on Android 7 Motorola devices as well?

@anukools @jpusp
Do you have any test devices where you have reproduced this issue? We haven't been able to reproduce it.

[jpusp]

I'm seeing this issue facing on few samsung devices too (samsung a5) with Android 7.
I didn't find a way to reproduce this bug. It appears when the user updates the app.

[jkasten2]

The issue seems to be related to the notifications being restored to the notification area when the app is updated from what you have noted and the crash logs.

Can you try the following to attempt to reproduce the issue.

1. Send a notification to the device.
2. run adb install -r your_app_name.apk. - This should simulate an update
3. Repeat - Specific types of notifications or a number of them maybe required to reproduce the issue.

@jpusp were you able to find a solution for this? I'm experiencing the same issue on the same devices

[LDALEGRIA]

We are having the same issue. Anyone on it?

[jkasten2]

@LDALEGRIA We haven't been able to reproduce this issue and the stack trace is showing the Android framework classes part of the Android OS itself. This make it difficult to know what is the root cause of the issue or if any attempted changes will have any effect.

Do you have any crash reports from any other version other than Android 7.0? Are you able to produce the crash on any of your test devices?

[LDALEGRIA]

@jkasten2

Attached you have my crash logs.
It's only happening to Android 7.0 and I have not been able to reproduce it.

br.com.evino.android_issue_160_crash_.txt
http://crashes.to/s/a4e6ad455c5

[jkasten2]

Thanks for the details, the issue seem isolated to just 7.0. We haven't seen any 7.1 reports but it's market share is 10x less than 7.0 as well. We will focus more testing on 7.0 to try to reproduce this issue.

Also what version of the com.android.support library does your project use? This is used by OneSignal to generate the notification so this can be a factor as well.

[LDALEGRIA]

@jkasten2 Thanks for checking.
We are using com.android.support library 24.2.1

Hopefully we can resolve this issue. Count on our help if needed.

[jpusp]

@PeteSesto I didnt find any solution for this.

@jkasten2 Yes, its happening on Android 7.0 only. My support library changed from 25.3.0, 25.4.0, 26.0.1 and 26.0.2 across the time. Nothing changes.

@LDALEGRIA Its almost the same crashlytics log that i have here. The difference is that some samsung devices is on the list (a few)

Motorola crashes
http://crashes.to/s/83a5dbe2cc5

Samsung crashes
http://crashes.to/s/aa15d2d48ce

[awsleiman171]

It seems like it's not only happening on 7.0 I have the same happening here on this device :
Android: 5.1
Android Build: TIT-U02C328B106
Manufacturer: HUAWEI
Model: HUAWEI TIT-U02

android.app.RemoteServiceException: Bad notification posted from package com.anghami: Couldn't expand RemoteViews for: StatusBarNotification(pkg=com.anghami user=UserHandle{0} id=١٠١ tag=null score=٠ key=0|com.anghami|101|null|10105: Notification(pri=0 contentView=com.anghami/0x109007e vibrate=null sound=null defaults=0x0 flags=0x62 color=0xff92278f category=transport actions=5 vis=PRIVATE))
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1653)
	at android.os.Handler.dispatchMessage(Handler.java:111)
	at android.os.Looper.loop(Looper.java:194)
	at android.app.ActivityThread.main(ActivityThread.java:5668)
	at java.lang.reflect.Method.invoke(Native Method)
	at java.lang.reflect.Method.invoke(Method.java:372)
	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:963)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:758)`

I'm using the support Lib : :26.0.2 and here's my code (note that all the Icons I'm using are SVGs) :

NotificationCompat.Builder builder = new NotificationCompat.Builder(this, CHANNEL_ID)
        .setSmallIcon(R.drawable.ic_notification)
        .setContentTitle(finalTitle)
        .setContentIntent(getMainPendingIntent())
        .setDeleteIntent(closePendingIntent)
        .setLargeIcon(bitmap)
        .setStyle(new android.support.v4.media.app.NotificationCompat.MediaStyle()
            .setMediaSession(new MediaSessionCompat(this, CHANNEL_ID).getSessionToken()).setShowActionsInCompactView(1, 2, 3))
        .setContentText(subtitle)
        .addAction(isLiked ? R.drawable.ic_like_filled_purple_26dp : R.drawable.ic_like_outline_purple_26dp, getString(isLiked?R.string.like:R.string.unlike), getPendingIntent(PlayerActions.ACTION_LIKE))
        .addAction(R.drawable.ic_previous_purple_18dp, getString(R.string.rewind), getPendingIntent(PlayerActions.ACTION_PREV))
        .addAction(playPauseRes, playPauseString, getPendingIntent(PlayerActions.ACTION_PLAY_PAUSE))
        .addAction(R.drawable.ic_next_purple_18dp, getString(R.string.next), getPendingIntent(PlayerActions.ACTION_NEXT))
        .addAction(R.drawable.ic_radio_filled_26dp, getString(R.string.radio), getPendingIntent(PlayerActions.ACTION_CURRENT_SONG_RADIO));
    builder.setColor(ContextCompat.getColor(this,R.color.purple));
    showNotification(builder.build());

[Alamgir]

@jpusp @LDALEGRIA Considering that the issue seems to happen on app updates, do you recall if your updated APK added/removed any resources (drawable or otherwise)?

We're considering the case where aapt has compiled a different set of resource IDs due to the resources being changed and there may be a corner-case condition where a resource ID becomes invalid after the apk is updated.