App Store Connect rejects ScreenPortSDK 1.0.0 (ITMS-90338)
We are integrating ScreenPort into Nobe OmniScope for iPad. App Store Connect accepted the upload, then rejected the build during processing because of selectors in the bundled SDK:
ITMS-90338: Non-public API usage - The app references non-public selectors in Frameworks/ScreenPortSDK.framework/ScreenPortSDK: backgroundColorWithTintColor:, boldFontOfSize:, dataSourceDidReloadData:, lightFontOfSize:, mediumFontOfSize:.
SDK and build
- ScreenPortSDK binary 1.0.0, obtained through the Swift package.
- Package revision: dd1fb84 (current main).
- Package.swift still downloads ScreenPortSDK-1.0.0.zip.
- Xcode 26.5, Release archive for arm64 iPadOS, minimum deployment target 16.4.
- Rejection received on 24 September 2026.
Could you provide an updated SDK that passes App Store Connect validation? If these are internal SDK methods whose names collide with Apple's private selectors, could they be renamed/prefixed in the SDK source and the binary rebuilt? We cannot resolve them in our app's source because the framework is distributed as a binary.
We also received a missing-dSYM warning for the SDK UUID AED00E60-E1FB-3BBB-8D6D-88B7DD6A8823. Please include matching dSYMs with the corrected release if possible. The embedded framework has no PrivacyInfo.xcprivacy; please also clarify/provide the appropriate privacy manifest and required-reason API declarations.
ScreenPort is temporarily excluded from our first TestFlight beta until a corrected SDK is available. Happy to validate an updated binary and report back.
App Store Connect rejects ScreenPortSDK 1.0.0 (ITMS-90338)
We are integrating ScreenPort into Nobe OmniScope for iPad. App Store Connect accepted the upload, then rejected the build during processing because of selectors in the bundled SDK:
SDK and build
Could you provide an updated SDK that passes App Store Connect validation? If these are internal SDK methods whose names collide with Apple's private selectors, could they be renamed/prefixed in the SDK source and the binary rebuilt? We cannot resolve them in our app's source because the framework is distributed as a binary.
We also received a missing-dSYM warning for the SDK UUID AED00E60-E1FB-3BBB-8D6D-88B7DD6A8823. Please include matching dSYMs with the corrected release if possible. The embedded framework has no PrivacyInfo.xcprivacy; please also clarify/provide the appropriate privacy manifest and required-reason API declarations.
ScreenPort is temporarily excluded from our first TestFlight beta until a corrected SDK is available. Happy to validate an updated binary and report back.