game-ci / game-ci/unity-builder
An option to create dSYM file for macOS
- Dominant language
- TypeScript
- Stars
- 1.1k
- Forks
- 313
- Avg merge
- 1h 39m
- Merged PRs (30d)
- 1
Description
**Context**
We received some crash reports for macOS but we cannot debug properly since we don't have the symbols.
**Suggested solution**
Add an option to create a dSYM file and upload xcarchive (maybe also dSYM for Unity) alongside the .app.
**Considered alternatives**
Building without unity-builder.
**Additional details**
Found some mention in Unity docs: [https://docs.unity3d.com/ru/2017.4/Manual/UnityPerformanceReportingFindingiOSSymbols.html](https://docs.unity3d.com/ru/2017.4/Manual/UnityPerformanceReportingFindingiOSSymbols.html)
The symbols should be useable as described in [https://developer.apple.com/documentation/xcode/adding-identifiable-symbol-names-to-a-crash-report#Symbolicate-the-crash-report-in-Xcode](https://developer.apple.com/documentation/xcode/adding-identifiable-symbol-names-to-a-crash-report#Symbolicate-the-crash-report-in-Xcode)
https://developer.apple.com/documentation/xcode/building-your-app-to-include-debugging-information#Publish-your-app-with-symbol-information
Contributor guide
Research direction
No implementation file or test is named. Start by tracing how macOS builds and artifacts are configured and uploaded, then inspect how Unity Builder options are exposed. Done means an opt-in dSYM and/or xcarchive is produced alongside the .app and can be used to symbolicate macOS crash reports.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, macos, typescript, unity
- Domain
- build-system, ci-cd, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100