[Bug] ANR traces are not symbolicated
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- unity
- Domain
- mobile-dev, observability-sre
Research direction
Start by reviewing the Crashlytics symbol-upload workflow described in the issue and compare it with Unity's Stacktrace Utility and its addr2line-based symbolication. Reproduce the Android IL2CPP ANR using the listed Unity and Firebase versions, then verify that the resulting Crashlytics trace is symbolicated rather than showing raw addresses.
Written by the indexing model from the issue text.
Description
[REQUIRED] Please fill in the following fields:
- Unity editor version: 2020.3.32f1
- Firebase Unity SDK version: 8.8.0
- Source you installed the SDK: .unitypackage
- Problematic Firebase Component: Crashlytics
- Other Firebase Components in use: Analytics
- Additional SDKs you are using: Facebook, Singular, AppLovin MAX SDK, AdMob, ironSource, AdColony,
- Platform you are using the Unity editor on: Windows 11 Pro
- Platform you are targeting: Android
- Scripting Runtime: IL2CPP
[REQUIRED] Please describe the issue here:
I can see my ANR in the Crashlytics but it is not symbolicated:

As a text:

Steps to reproduce:
It is 100% reproducible.
- I am building the game locally;
- Then I upload symbols using Firebase CLI and it works as expected:
Crashlytics symbol file uploaded successfully; - Then I run the game and generate an ANR making an infinite loop in the
mainthread. - I see my ANR report in the Firebase Crashlytics but it is not symbolicated.
The interesting part:
I used Unity's Stacktrace Utility (comes with Android Logcat package) to symbolicate this stack trace using the same symbols I uploaded earlier to Crashlytics and it works as expected:

Under the hood this utility uses addr2line so I guess this proves that this trace definitely can be symbolicated!
- Dominant language
- C#
- Stars
- 923
- Forks
- 456
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from firebase/quickstart-unity
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
firebase/quickstart-unity#1448 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
firebase/quickstart-unity#1432 · 1 comment ·
-
new
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
firebase/quickstart-unity#1411 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
firebase/quickstart-unity#1403 · 1 comment ·
-
Firebase or specific Android versions trigger app_clear_data on first_open, disrupting our funnel Opennew
Difficulty 4/5 3-5 days Newbie friendliness 25/100
firebase/quickstart-unity#1390 · 1 comment ·
All issues in firebase/quickstart-unity
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·