Open aboulianne-ludia opened 1 month ago
Hi @aboulianne-ludia, thank you for reaching out. I tried reproducing the issue, however, I did not encounter the crash. With the metrics you shared and given that this is difficult to reproduce, this seems to be an edge case scenario.
I'll raise this to our engineers with the possible fix you raised (Adding null check on the rootView element) and see what we can do here. Thanks!
[REQUIRED] Step 2: Describe your environment
[REQUIRED] Step 3: Describe the problem
In our live app built with Unity (2022.3.27f1), our top crash (600 events daily but less than 1% of our sessions) used to happen when our UnityPlayerActivity would receive onResume. (call stack will be shown below). Looking at the code of AppStartTrace.java at line 355 (at revision a350561 on April 25th, 2024 ), the line is:
It is unclear why, in certain cases, line 354 would return null. The crash disappeared when we disabled ExperimentTTID by adding
<meta-data android:name="experiment_app_start_ttid" android:value="false" />
to our AndroidManifest.xmlWe have never reproduced the issue internally, or never noticed that it happened. It seems to happen on Android 12 and above.
Would a null check against rootView resolve the issue? Or is there a deeper reason and that value should never be null? Since our app is large, maybe the view hasn't finished initialization at that point? (Google Play vitals has flagged our Warm app start metric as problematic, if that helps.)
Steps to reproduce:
truncated call stack of crash:
Relevant Code: