skip export should include debug symbols for native Swift code in the .aar
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 3.2k
- Forks
- 106
- Avg merge
- 6d 13h
- Merged PRs (30d)
- 1
Description
Discussed in https://github.com/orgs/skiptools/discussions/523
Originally posted by vdkdamian October 29, 2025
Small question,
Is there a reason my Build Settings where as following:
DEBUG_INFORMATION_FORMAT = "dwarf"?
I now manually set this to DEBUG_INFORMATION_FORMAT = "dwarf-with-dsym".
I kept getting a warning when uploading the archive to TestFlight. Also saw this warning when uploading the .aab to Google Play.
It solved the warning for TestFlight, but on Google Play I keep getting the warning:
Google Play warning:
This App Bundle contains native code, and you haven't uploaded any debug symbols. We recommend uploading a symbol file so your crashes and ANRs can be more easily analyzed and resolved.
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.
Research direction
Start with the Skip export/build path that produces the Android .aar and inspect how debug information is configured and packaged for native Swift code. Verify the resulting .aar includes debug symbols and that the Google Play warning is addressed when the artifact is uploaded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, swift
- Domain
- build-system, mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100