Same problem for a macOS Catalyst app that had several builds accepted until just recently. Frameworks (via Cocoapods) were flagged for:ITMS-90338: Non-public API usage - The app references non-public symbols..._SecItemAdd, _SecItemCopyMatching, _SecItemDelete, _SecItemUpdate, _kSecAttrAccessible, _kSecAttrAccessibleWhenUnlocked, _kSecAttrAccount, _kSecAttrLabel, _kSecAttrService, _kSecClass, _kSecReturnData, _kSecValueData
millerjasonw
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
The problem seems to have disappeared without any clear cause here. Only changes here were:no longer deriving the catalyst bundle id for the separate mac target (separate target may eventually go away)defaulting the target's Release provisioning to a Developer ID Application profile and Deverloper ID Application identity (for AppCenter distribution)using Fastlane update_project_provisioning to switch the target's Release provisioning to Mac Store profile and Apple Distribution identity when archiving for Mac Store upload (previously this was the default that was failing, no reason to think any different)