You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since a date between Dec 4th 2024 and Dec 12th, I have a sudden rise of a crash in Firebase Crashlytics. This rise is not linked to an update of our app as it has not been updated during this period. I see that:
Noe that it is not sure if this problem induces a crash ; indeed the Crashlytics crash log below shows that the error is described as both "fatal" and "non fatal". We have not received any complains so we expect that the issue is non fatal but not sure. Also, Crashlytics shows that our "Crash free user rate" remains close to 100% and didn't change in December 2024.
Crashlytics also does not show any rise of the ANR rate in December 2024.
According to Crashlytics, this error happens with approximately 3.5% of our users.
Note that in Android Vitals (Google Play Console), we don't see any rise of the crash rate but we see an unexplained rise of ANR from Dec 10th. It is very weird as, as already explained, we see the contrary in Crashlytics: rise of the crash rate (not sure if fatal or not) and stable ANR rate.
Please tell us what is happening, solve the issue or tell us how to solve it. Thanks a lot.
VERSIONS USED
Android Studio: NA
ARCore SDK for Android: 1.47.0
Device manufacturer, model, and O/S: All
Google Play Services for AR (ARCore): updated 4 dec. 2024
STEPS TO REPRODUCE THE ISSUE
Unable to reproduce on our test devices. Not sure if the issue induces a crash (not clear if it is fatal or not fatal).
WORKAROUNDS (IF ANY)
Not found any.
ADDITIONAL COMMENTS
Crash log:
**Non-fatal** Exception: java.lang.Exception: com.google.ar.core.exceptions.FatalException
at com.mycompany.myapp.GLSurfaceRenderer.onDrawFrame(GLSurfaceRenderer.java:2044)
at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1573)
at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1272)
Caused by com.google.ar.core.exceptions.**FatalException**:
at java.lang.reflect.Constructor.newInstance0(Constructor.java)
at java.lang.reflect.Constructor.newInstance(Constructor.java:343)
at com.google.ar.core.Session.throwExceptionFromArStatus(Session.java:16)
at com.google.ar.core.Session.nativeCreateAnchor(Session.java)
at com.google.ar.core.Session.createAnchor(Session.java:1)
at com.mycompany.myapp..GLSurfaceRenderer.onDrawFrame(GLSurfaceRenderer.java:908)
at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1573)
at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1272)
The text was updated successfully, but these errors were encountered:
SPECIFIC ISSUE ENCOUNTERED
Since a date between Dec 4th 2024 and Dec 12th, I have a sudden rise of a crash in Firebase Crashlytics. This rise is not linked to an update of our app as it has not been updated during this period. I see that:
Noe that it is not sure if this problem induces a crash ; indeed the Crashlytics crash log below shows that the error is described as both "fatal" and "non fatal". We have not received any complains so we expect that the issue is non fatal but not sure. Also, Crashlytics shows that our "Crash free user rate" remains close to 100% and didn't change in December 2024.
Crashlytics also does not show any rise of the ANR rate in December 2024.
According to Crashlytics, this error happens with approximately 3.5% of our users.
Note that in Android Vitals (Google Play Console), we don't see any rise of the crash rate but we see an unexplained rise of ANR from Dec 10th. It is very weird as, as already explained, we see the contrary in Crashlytics: rise of the crash rate (not sure if fatal or not) and stable ANR rate.
Please tell us what is happening, solve the issue or tell us how to solve it. Thanks a lot.
VERSIONS USED
STEPS TO REPRODUCE THE ISSUE
Unable to reproduce on our test devices. Not sure if the issue induces a crash (not clear if it is fatal or not fatal).
WORKAROUNDS (IF ANY)
Not found any.
ADDITIONAL COMMENTS
Crash log:
The text was updated successfully, but these errors were encountered: