iOS Notification Service Extension – Dynamic XCFramework causes App Store rejection

Follow

We are integrating Airship Notification Service Extension using XCFrameworks.

We verified AirshipNotificationServiceExtension.xcframework using otool -L and confirmed it is dynamically linked:

@rpath/AirshipNotificationServiceExtension.framework/AirshipNotificationServiceExtension

To make rich push images work, the framework must be Embed & Sign in the Notification Service Extension target. However, this creates a Frameworks/ directory inside the .appex, and App Store / TestFlight validation fails with:

“Invalid Bundle – Notification Service Extension contains disallowed nested bundles / Frameworks directory.”

Dynamic frameworks embedded in a Notification Service Extension are rejected by Apple.

Request:
Please provide a STATIC Notification Service Extension XCFramework (or an App-Store-approved integration method) for iOS rich push images.

This is currently blocking our App Store release.