ITMS-90158

Project Background: I developed a Mac project using Electron and VSCode Successfully uploaded the packaged pkg using Transporter, However, I will receive an email informing me that there are some issues with the project: ITMS-90296: App sandbox not enabled - The following executors must include the 'com. apple. security. app sandbox' entitlement with a Boolean value of true in the entitlement property list: [[com. electron. iflyrecclient. pkg/Payload/iFlytek Listen. app/Contents/MacOS/iFlytek Listen]] ITMS-90886: 'Cannot be used with TestFlight because the signature for the bundle at' iFlytek hears. app 'is missing an application identifier but has an application identifier in the provisioning profile for the bundle.' Bundles with application identifiers in the provisioning profile are expected to have the same identifier signed into the bundle in order to be eligible for TestFlight.' Here is my packaging process: Generate an app using the electron packager tool Sign the app using @ electron

Hello! I encountered an issue while packaging and uploading the project to the Mac store. I received an email stating: ITMS-90296: App Sandbox not enabled - The following executors must include the 'com. apple. security. app sandbox' entitlement with a Boolean value of true in the entitlement property list: [[com. electron. iflyrecclient. pkg/Payload/iFlytek Listen. app/Contents/MacOS/iFlytek Listen]] Refer to App Sandbox page at https://developer.apple.com/documentation/security/app_sandbox for more information on sandboxing your app. Though you are not required to fix the following issues, we wanted to make you aware of them: ITMS-90886: 'Cannot be used with TestFlight because the signature for the bundle at' iFlytek hears. app 'is missing an application identifier but has an application identifier in the provisioning profile for the bundle.' Bundles with application identifiers in the provisioning profile are expected to have the same identifier signed into the bundle in order to be eligi

We just compiled and uploaded new release with Xcode 16.1 to the App Store. A few minutes later the following email arrived: The app references non-public selectors in {app_name}: setNavigationBar:. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. But we don’t have any setNavigationBar methods in our project. Only setNavigationBarHidden calls for navigationController. And this is not private API of course. Please let us know how to upload our update for review. Thank you!

Hello developers ! My team and I are currently trying to migrate to the new Xcode 16 version. We encounter a blocker problem with the new Xcode when submitting a new build on TestFlight. The problem : ITMS-90338: Non-public API usage - The app references non-public selectors in AccorHotelsApp: setSupportedInterfaceOrientations:. We tried several things to solve the issue : remove all the frameworks that are not built by us ; the issue is still present remove the code related to this API in our base code and the frameworks ; the issue is fixed remove only the code related to this API in our base code ; the issue is fixed This indicates that the problem is the code related to this API. The code removed : override public var supportedInterfaceOrientations: UIInterfaceOrientationMask { get { configuration.orientation } set { _ = newValue } } This code is located in our local SPM. It's used to handle orientation of our app depending on specifics configuration given as a parameter. Why Xcode 16 is detectin

Hello, I had app written in React Native using Expo. Now, I cleared up Expo from project, created new project, moved old source file to new project. Everything works fine. Now I want to publish new project using old bundle id to overwrite existing app, but I can't. What is problem? Is not permitted to do that? Maybe I need to provide something additionally? Thank you for helping.

I received the follow error result and based on my research, it seems that it may be a false positive. Web3podium Version 1.0.8 Build 45 Please correct the following issues and upload a new binary to App Store Connect. ITMS-90338: Non-public API usage - The app references non-public selectors in Frameworks/JitsiMeetSDK.framework/JitsiMeetSDK: initWithURLStrings:. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/ ITMS-90683: Missing purpose string in Info.plist - Your app’s code references one or more APIs that access sensitive user data, or the app has one or more entitlements that permit such access. The Info

Hello, i know this topic is here since ever, also in other forums, however this topic i face for a month and cant get pass it, I tried all other suggestions which didnt bring me anywhere. so, project using cmake in order for Qt creator (so c++ base project with enabled swift), however once i run a cmake which generates *.xcodeproj for Xcode, i open it via xcode and can properly build and deploy to device. however when I try to archive and sent to Testflight/AppStore, I get: ITMS-90426: Invalid Swift Support and when I try to followup guides to create it manualy, copying libs from: $(TOOLCHAIN_DIR)/usr/lib/swift-5.0/$(PLATFORM_NAME) plese here note, that ALL guides indicate to use folder swift, however there are no *.dylib files... they are only in swift-5.0 folder then I receive an error type: ITMS-90429: Invalid Swift Support - The files libswiftMetal.dylib, libswiftHomeKit.dylib, libswiftsimd.dylib, libswiftCallKit.dylib, libswiftos.dylib, libswiftNetwork.dylib, libswiftMapKit.dylib, libsw

We have a CD pipeline set up for many apps (we're an app dev agency, we're uploading apps all the time). Uploads of our apps to AppStoreConnect using the iTMSTransporter command line tool started failing a few days ago. If we attempt to upload the same bundle using the Mac Transporter app, it uploads just fine. The problem only seems to be the iTMSTransporter command line tool. The version of the tool we're using is: iTMSTransporter, version 3.3.0 I've also tried running these commands pointing at the version of iTMSTransporter running at /Applications/Transporter.app/Contents/itms/bin/iTMSTransporter but this won't even start due to some Java security certificate issue. An example of the command we are calling is: /usr/local/itms/bin/iTMSTransporter -m upload -v eXtreme -f /path/to/Bundle.itmsp -jwt {generatedJwtHere} The bundle appears to actually upload to the AppStore OK, after lots of logs we get a message like: INFO: Reservation committed: (CPUSource221/v4/0b/e5/74/0be57409-0479-3c02-0

I am trying to set up a workflow where Apple Vision Pro users in my organization can install a signed enterprise .ipa file from an internal web page. The relevant link looks something like this: <a role=button href=itms-services://?action=download-manifest&url=https://my.example.com/path/manifest.plist>Click here to download</a> After verifying that all the mime types were correct on the server and the certificate was valid, I finally attached my AVP headset to my Mac's console app and saw that the errors look like this: [com.example.myapp] Skipping due to incompatible platform: com.apple.platform.xros Could not load download manifest with underlying error: Error Domain=ASDErrorDomain Code=752 Not compatible with this platform: com.apple.platform.xros UserInfo={NSDebugDescription=Not compatible with this platform: com.apple.platform.xros} This manifest.plist was made by the Distribute App workflow in Xcode 16.0. Multipart question: Is installing VisionOS apps via m

I am running the iTMS Transporter on a OL7 k8s pod. The issue appeared when I have set the read-only filesystem. Trace: Exception in thread main java.lang.ExceptionInInitializerError at com.apple.transporter.launcher.Application.start(Application.java:120) at com.apple.transporter.launcher.Application.main(Application.java:766) Caused by: java.lang.NullPointerException: Cannot invoke com.apple.transporter.launcher.api.LaunchLogger.warn(String) because com.apple.transporter.launcher.util.FileUtil.logger is null at com.apple.transporter.launcher.util.FileUtil.logWarning(FileUtil.java:151) at com.apple.transporter.launcher.util.FileUtil.userHomeDirectory(FileUtil.java:110) at com.apple.transporter.launcher.util.FileUtil.localConfigHome0(FileUtil.java:188) at com.apple.transporter.launcher.util.FileUtil.(FileUtil.java:25) ... 2 more I have to have the pod filesystem read-only it is a security compliance requirement, so I need to find a solution for this issue. Before setting the the FS to read-only every