Skip to content

NPE in obfuscated code after calling trace.stop() #1383

@sn-michiyo

Description

@sn-michiyo

Describe your environment

  • Android Studio version: 3.6.1
  • Firebase Component: Performance
  • Component version: 19.0.0

Describe the problem

Crashlytics is reporting 80 users experiencing a null pointer exception When calling trace.stop(); We haven't seen this during development and trace object itself itsn't null; the crash comes in the obfuscated firebase code. Is there anything we can to prevent the crash?

Fatal Exception: java.lang.NullPointerException
Attempt to invoke virtual method 'com.google.android.gms.internal.firebase-perf.zzcr com.google.firebase.perf.internal.zzq.zzbf()' on a null object reference
com.google.firebase.perf.internal.zzq.zza (zzq.java:39)
com.google.firebase.perf.metrics.zzd.zzcd (zzd.java:20)
com.google.firebase.perf.metrics.Trace.stop (Trace.java:87)

app-level build.gradle:

implementation 'com.google.firebase:firebase-perf:19.0.0'
...
apply plugin: 'com.google.firebase.firebase-perf'

I don't see anything in the Trace docs about NPEs, and didn't find any mention of this in the issues for this repo.

I also looked at the release notes for Performance Monitoring for 19.0.1, 19.0.2, 19.0.3, 19.0.4, and 19.0.5 for mention of a NPE to see if upgrading would fix the issue, but don't see any mention of it.

Metadata

Metadata

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions