ITMS-90338

1,570 results found

Post

Replies

Boosts

Views

Activity

Error when uploading eBook
I'm trying to upload my ebook, which gives me this error. I checked the EPUB file, and it is ok. Can anyone please assist me in solving this? Package Summary: 1 package(s) were not verified because they had problems: /tmp/package.itmsp - Error Messages: ERROR ITMS-4340: Content cannot be delivered until compliance information regarding your account is provided and verified in iTunes Connect. at Book/BookMetadata Request ID: 77b8bc43-77fb-44ff-9f49-a2eb85b088cd
0
0
92
1w
App alternative icon not working when archieve.
I add the following info in the build settings of my app. Then I also add the icon to my asset. I build the app, it works normally, but I notice that when I changed the icon to 'AppIcon-Defaults', The icon change alert didn't appear. but it succeeds . I uploaded the archive to App Store I got: ITMS-90895: Missing Icon - The Info.plist key CFBundleIcons.CFBundleAlternateIcons contains an entry “AppIcon-Defaults” that references asset “AppIcon-Defaults.” No such asset is present in the asset catalog. Then I use xcrun --sdk iphoneos assetutil --info Assets.car to check the assets inside the archieved app, It have the asset.
1
0
117
1w
Reply to Pkg installation package uploaded to macstore email prompt ITMS-90296
I tried using a third-party app (Pacivist) to open the app in pkg, nd export the app locally,then followed your instructions to perform the following actions: 1、 Run codesign against the results app to confirm that its signature is valid: % codesign --verify -vvv /path/to/your.app The results obtained: PS:I noticed an error message IFlytek heard. app: a sealed resource is missing or invalid File missing:/Users/pploo2/Desktop/icon/1/iFlytek heard. app/Contents/Resources/tj_S1/_MACOSX/ node_modules I don't know if this is the key to the problem ITMS-90926. 2. Run codesign again to check that you have App Sandbox enabled: % codesign --display --entitlements - /path/to/your.app The results obtained: You can see that there is sandbox=true here Now back to the first step, I performed operations on the app before packaging it as pkg and found that there were no missing related issues
1w
Reply to Pkg installation package uploaded to macstore email prompt ITMS-90296
First things first, the TestFlight issue (ITMS-90886) is covered by TestFlight, Provisioning Profiles, and the Mac App Store. Regarding the App Sandbox issue (ITMS-90296), there’s a variety of potential causes for this. I recommend that you check whether App Sandbox is actually enabled on the binary that you submitted to App Store Connect. To do that: Locate the installer package (.pkg) you submitted. Unpack that. I usually do this with a third-party app (Pacifist), but Unpacking Apple Archives explains how to do it the hard way. Run codesign against the resulting app to confirm that its signature is valid: % codesign --verify -vvv /path/to/your.app Run codesign again to check that you have App Sandbox enabled: % codesign --display --entitlements - /path/to/your.app I’d expect to see output like this: % codesign --display --entitlements - /Applications/PCalc.app … [Dict] … [Key] com.apple.security.app-sandbox [Value] [Bool] true … Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical S
1w
Pkg installation package uploaded to macstore email prompt ITMS-90296
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
1
0
190
1w
Pkg installation package uploaded to macstore email prompt ITMS-90296
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
16
0
443
2w
ITMS-90338: Non-public API usage
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!
1
0
160
2w
ITMS-90338: Non-public API usage : setSupportedInterfaceOrientations
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
1
0
150
2w
ITMS-90129: The bundle uses a bundle name or display name that is already taken
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.
0
0
110
2w
Reply to iTMSTransporter -m upload fail
Hi @barisunz, I faced the same error yesterday (Step ). I'm not sure if the reason of the error is the same, anyway I performed the following step in order to solve the upload problem: uninstalled the Transporter.app (useless in my case) installed the iTMSTransporter from the link mentioned by @JZ4L3SK1 updated fastlane version (the idea behind the most recent fastlane version is to search the iTMSTransporter bin in the /usr/local/itms folder, unless you hard coded the itms path in the FASTLANE_ITUNES_TRANSPORTER_PATH ENV var) removed old ENV config hard coded in the fastlane script that was forcing fastlane to use the iTMSTransporter version bundled with Transport.app (that is older) After that, fastlane script was able to run the newest iTMSTransporter version and it was not necessary to switch to altool. Let me know if it can be helpful.
2w
JitsiMeetSDK Build Issues: False Positive?
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
0
0
120
2w
Invalid Swift Support Upon Submit to Testflight/AppStore
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
1
0
218
3w