NativeScript / NativeScript/plugins
[local-notifications] Prebuilt LocalNotificationsPlugin.xcframework ships without dSYMs — App Store Connect "Upload Symbols Failed" warning + unsymbolicatable crash frames
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- TypeScript
- Estrellas
- 206
- Forks
- 123
- Merge medio
- 2 d 1 h
- PR fusionados (30 d)
- 1
Descripción
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.
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Línea de trabajo
Empieza por localizar el flujo de trabajo de build y packaging que produce LocalNotificationsPlugin.xcframework y el paquete npm publicado. Comprueba cómo se archiva el framework y si sus dSYMs están incluidos en el release o adjuntos a él; verifica el resultado con los UUIDs indicados y con una carga de un archivo de App Store Connect.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- ios
- Área
- build-system, mobile-dev, release
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Tranquilo
- Claridad
- Bastante claro
- Aptitud para principiantes
- 45/100