The published xcframework contains no .dSYM bundles, and the binaries are stripped (dwarfdump reports 0 DWARF source entries). As a result:
- Every App Store upload emits
Upload Symbols Failed. The archive did not include a dSYM for the WebRTC.framework with the UUIDs [...]
- Crash reports that land inside WebRTC show only a raw offset (e.g.
WebRTC 0x... + 7674808), with no function names.
Concretely: we recently traced a crash affecting 97% of our reports to a single offset inside WebRTC during peer connection teardown. We could tell that 34 of 35 reports shared the same offset, so we knew it was one bug — but we could not tell which function it was, which made the fix largely guesswork.
Would you consider publishing the .dSYM bundles as part of the release (either inside the xcframework, or as a separate archive attached to the GitHub release)? That would let app developers upload them to App Store Connect and get readable stack traces.
Version in use: 151.x
The published xcframework contains no
.dSYMbundles, and the binaries are stripped (dwarfdumpreports 0 DWARF source entries). As a result:Upload Symbols Failed. The archive did not include a dSYM for the WebRTC.framework with the UUIDs [...]WebRTC 0x... + 7674808), with no function names.Concretely: we recently traced a crash affecting 97% of our reports to a single offset inside WebRTC during peer connection teardown. We could tell that 34 of 35 reports shared the same offset, so we knew it was one bug — but we could not tell which function it was, which made the fix largely guesswork.
Would you consider publishing the
.dSYMbundles as part of the release (either inside the xcframework, or as a separate archive attached to the GitHub release)? That would let app developers upload them to App Store Connect and get readable stack traces.Version in use: 151.x