NativeScript / NativeScript/plugins
[local-notifications] Prebuilt LocalNotificationsPlugin.xcframework ships without dSYMs — App Store Connect "Upload Symbols Failed" warning + unsymbolicatable crash frames
还没有人认领这个 Issue。
- 主要语言
- TypeScript
- 星标
- 206
- 派生
- 123
- 平均合并
- 2 天 1 小时
- 30 天内合并 PR
- 1
描述
Plugin
@nativescript/local-notifications 6.4.0 (latest published at time of filing)
Issue
The iOS LocalNotificationsPlugin.xcframework in the published npm package is a prebuilt binary that does not include (or ship alongside) its dSYM debug symbols. Consequences for every app using the plugin:
-
Every App Store Connect upload finishes with a warning — "Upload Symbols Failed":
The archive did not include a dSYM for the LocalNotificationsPlugin.framework with the UUIDs [9C2B11C2-766D-3635-8D8F-F69FF79669FD, DE242052-9F7D-3646-BC6D-9D78B7994234]. Ensure that the archive's dSYM folder includes a DWARF file for LocalNotificationsPlugin.framework with the expected UUIDs.
(UUIDs as reported by App Store Connect for 6.4.0.)
-
Production crash frames inside the plugin cannot be symbolicated. dSYMs can only be produced by the compilation that built the binary, so consumers of the prebuilt framework have no way to generate them — a crash pointing into the plugin stays as raw addresses.
Reproduction
Archive any NativeScript iOS app that depends on @nativescript/local-notifications and upload it via Xcode Organizer → the "Upload Symbols Failed" warning above appears (upload itself succeeds).
Request
Please ship the framework's dSYMs so consumers can symbolicate plugin frames and uploads run clean. Either:
- include the dSYMs inside the published xcframework (e.g. archive with
DEBUG_INFORMATION_FORMAT=dwarf-with-dsymand package*.framework.dSYMper slice / use-debug-symbolswithxcodebuild -create-xcframework), or - attach the dSYM zip to the corresponding GitHub release so it can be uploaded to App Store Connect manually.
Thanks — the plugin itself works great; this is purely about crash-report observability for the binary you build for us.
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
首先定位生成 LocalNotificationsPlugin.xcframework 和已发布 npm package 的 build 和 packaging workflow。检查 framework 的归档方式,以及其 dSYMs 是否包含在 release 中或附加到 release;根据报告的 UUIDs 和一次上传到 App Store Connect 的 archive 验证结果。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- ios
- 领域
- build-system, mobile-dev, release
- Issue 类型
- 缺陷
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 冷清
- 描述清晰度
- 基本清楚
- 新手友好度
- 45/100