[Bug] unity ios crash log can't restore li2cpp stack symbol but the third party Library is fine

Open
#1,200 19 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp, firebase, ios, unity
Domain
mobile, observability-sre

Research direction

Start with the attached Code.zip and the Unity 2018.4.23f1 project, then reproduce the iOS IL2CPP crash through the listed Xcode Archive and upload-symbols steps. Compare the resulting Firebase Crashlytics report with the dSYM in the .xcarchive; done means the IL2CPP stack symbols are restored while third-party library symbols remain correct.

Written by the indexing model from the issue text.

Description

api: crashlytics needs-attention type: question
[REQUIRED] Please fill in the following fields:
  • Unity editor version: 2018.4.23f1
  • Firebase Unity SDK version: 8.6.2
  • Source you installed the SDK: .unitypackage
  • Problematic Firebase Component: Crashlytics
  • Other Firebase Components in use: Google Analytics
  • Additional SDKs you are using: none
  • Platform you are using the Unity editor on: mac
  • Platform you are targeting: iOS
  • Scripting Runtime: IL2CPP
[REQUIRED] Please describe the issue here:

问题截图

Steps to reproduce:

1、Create empty unity project
2、Set up filebase sdk width Crashlytics and Analytics
3、Write some crash code and trigger with button click event.
4、Build the project with ios and install on the iphone
5、Open The Xcode Project And Run Product->Archive
6、Open the Xcode Organizer window and Find the dSYM file in .xcarchive
7、Upload dSYM file width command "/path/to/pods/directory/FirebaseCrashlytics/upload-symbols -gsp /path/to/GoogleService-Info.plist -p ios /path/to/dSYMs"
8、Click the button and the app will crash
9、See the creash report on firebse crashlytics

Relevant Code

Code.zip

Dominant language
C#
Stars
923
Forks
456
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from firebase/quickstart-unity

All issues in firebase/quickstart-unity

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.