[local-notifications] Prebuilt LocalNotificationsPlugin.xcframework ships without dSYMs — App Store Connect "Upload Symbols Failed" warning + unsymbolicatable crash frames

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:

1. 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.)

2. 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-dsym and package *.framework.dSYM per slice / use -debug-symbols with xcodebuild -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.

Start by locating the build and packaging workflow that produces LocalNotificationsPlugin.xcframework and the published npm package. Check how the framework is archived and whether its dSYMs are included or attached to the release; verify the result against the reported UUIDs and an App Store Connect archive upload.