[CRASHLYTICS] Android native crashes only have "???" in the title
I'm seeing a strange issue where native Android crashes show up in Crashlytics with "???" as the title instead of something more useful. I'm not sure if this is expected behaviour but it doesn't feel like it.
Setup: Unity Version: 2019.4.26f1 Firebase Version: 8.8.0
STR:
-
Setup up the quickstart-unity project for Crashlytics.
-
Build for Android
-
Trigger a native crash* and re-open the app.
-
(Optional) Upload the symbol files
-
Go to the Crashlytics dashboard and see the crash ** It should have a title "???"
-
I used this method to trigger a native crash however it also appears in our production environment for native other native crashes:
public void ThrowNativeCrash()
{
// https://stackoverflow.com/questions/17511070/android-force-crash-with-uncaught-exception-in-thread
var message = new AndroidJavaObject("java.lang.String", "This is a test crash, ignore.");
var exception = new AndroidJavaObject("java.lang.Exception", message);
var looperClass = new AndroidJavaClass("android.os.Looper");
var mainLooper = looperClass.CallStatic<AndroidJavaObject>("getMainLooper");
var mainThread = mainLooper.Call<AndroidJavaObject>("getThread");
var exceptionHandler = mainThread.Call<AndroidJavaObject>("getUncaughtExceptionHandler");
exceptionHandler.Call("uncaughtException", mainThread, exception);
}
Also, I followed the steps here to upload the symbols to Crashlytics and it seemed to make no difference.
Would love to hear an update about this. Having something similar happening to me
Having similar issue where a group of different crashes are grouped.
Unity: 2020.3.33f1 Firebase: 8.9.0
Hey folks, this can happen if no symbols are uploaded for that crash. Are you getting readable stacktraces for other native crashes in your app?
Hey @jamier-hh. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.
If you have more information that will help us get to the bottom of this, just add a comment!
Since there haven't been any recent updates here, I am going to close this issue.
@jamier-hh if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.