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
Don't send fatal uncaught exception if an NDK crash exists (#3020)
Our backend expects at most one fatal event per session. In some cases,
such as Unity, the native signal handler may cause an uncaught exception
to be thrown, after we have recorded the NDK crash. If this happens,
Crashlytics should ignore the uncaught exception and send the NDK
crash information as the fatal event.
Copy file name to clipboardExpand all lines: firebase-crashlytics/src/main/java/com/google/firebase/crashlytics/internal/CrashlyticsNativeComponent.java
Copy file name to clipboardExpand all lines: firebase-crashlytics/src/main/java/com/google/firebase/crashlytics/internal/CrashlyticsNativeComponentDeferredProxy.java
+6Lines changed: 6 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -40,6 +40,12 @@ public CrashlyticsNativeComponentDeferredProxy(
Copy file name to clipboardExpand all lines: firebase-crashlytics/src/main/java/com/google/firebase/crashlytics/internal/common/CrashlyticsController.java
+2-1Lines changed: 2 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -156,7 +156,8 @@ public void onUncaughtException(
Copy file name to clipboardExpand all lines: firebase-crashlytics/src/main/java/com/google/firebase/crashlytics/internal/common/CrashlyticsUncaughtExceptionHandler.java
0 commit comments