Closed Bug 1639891 Opened 5 years ago Closed 5 years ago

Crash in [@ [INFO] MalformedMessage(message=parsing encrypted message failed: at mozilla.components.lib.push.firebase.AbstractFirebasePushService.onMessageReceived(AbstractFirebasePushService.kt:14)]

Categories

(GeckoView :: General, defect)

Unspecified
Android
defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: RyanVM, Unassigned)

Details

(Keywords: crash)

Crash Data

This bug is for crash report bp-a11406ee-46a9-405c-8c72-eec1e0200521.

Currently, this is showing up as a top"crash" in Fenix (though I'm told this isn't actually causing crashes in the wild).

Java stack trace:

[INFO] MalformedMessage(message=parsing encrypted message failed
	at mozilla.components.lib.push.firebase.AbstractFirebasePushService.onMessageReceived(AbstractFirebasePushService.kt:14)
	at org.mozilla.fenix.push.FirebasePushService.onMessageReceived(FirebasePushService.kt:1)
	at com.google.firebase.messaging.FirebaseMessagingService.zzd(Unknown Source:176)
	at com.google.firebase.iid.zzg.run(Unknown Source:5)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
	at com.google.android.gms.common.util.concurrent.zza.run(Unknown Source:2)
	at java.lang.Thread.run(Thread.java:919)
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID

I can confirm, this isn't a bug but a info (as noted by the [INFO] in the trace) which seems to show up as a crash in Socorro. After May 13th we no longer even send this.

After speaking with Roger, it seems the reason this is marked as a top crash is because we're discarding crash info for anything longer than 2 weeks ago, so the "crash" rate of 50+% in Fenix 5.0.0 is misleading.

You need to log in before you can comment on or make changes to this bug.