ITMS-90338

Hi Everyone, I have an iPhone app with watch app and extension. I'm getting the following error when building: ITMS-90477: Invalid Bundle Identifier - Attempting to change bundle identifier from com.company.myapp.watchkitapp to com.company.myapp.watchkitappp is disallowed for bundle My App.app/Watch/My App Watch.app. The thing is I always used the second id (yes with triple p). I already check my identifiers on developer.apple site, there is no identifier with watchkitapp but watchkitappp is. Same for the XC side. When I trying to get first id I get; An App ID with Identifier 'com.company.myapp.watchkitapp' is not available. Please enter a different string. Any help is appreciated. Thx.

Hi, I am trying to run xcrun altool --list-providers -u my@email.com -p my-application-specific-password My console response looks as follows with a -24169 error when trying to authenticate. I have used this application password in the past with fastlane, but I do not seem to be able to authenticate today. 2023-02-17 10:09:28.753 Initializing bundle from: /Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/Versions/A/Frameworks/AppStoreService.framework 2023-02-17 10:09:28.762 Will look for transporter at executable bundle relative path: /Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/itms/bin/iTMSTransporter 2023-02-17 10:09:28.762 Looking for Transporter at path: /Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/itms/bin/iTMSTransporter 2023-02-17 10:09:28.762 Looking for Transporter at path: /Applications/Xcode.app/Contents/Developer/usr/bin/../SharedFrameworks/ContentDeliveryServices.fra

While attempting to upload my app to TestFlight (which has already been uploaded numerous times, including just a few days ago with the same code base) there is this error TMS-90338: Non-public API usage - The app references non-public selectors in : _isKeyDown, _modifiedInput, _modifierFlags..... Nothing new there, that's been happening for months for myself and countless others and has been reported numerous times, i.e. https://developer.apple.com/forums/thread/127678?answerId=715975022#715975022 https://developer.apple.com/forums/thread/714450 But now there's a difference - in the past the builds always appeared in Testflight after getting this warning, so it wasn't an issue. But now that's changed, the build is no longer appearing in Testflight, so it suddenly is a very big issue.

I have a Mac app that was accepted to the App Store when I built it using Xcode 13 (with code signing set to automatic, just like I do now), but with Xcode 14.2 I keep getting mails with ITMS-90288: Invalid Code Signing Entitlements and TMS-90286: Invalid Code Signing Entitlements, two very similar errors for each embedded dynamic library. The exact wording is this: TMS-90288: Invalid Code Signing Entitlements - The entitlements in your app bundle signature do not match the ones that are contained in the provisioning profile. According to the provisioning profile, the bundle contains a key value that is not allowed: '(My team id).' for the key 'com.apple.application-identifier' in 'Spatterlight.app/Contents/Frameworks/libc64diskimage.dylib' ITMS-90286: Invalid Code Signing Entitlements - Your application bundle's signature contains code signing entitlements that are not supported on macOS. Specifically, value '(My team id).' for key 'com.apple.application-identifier' in 'Spatterlight.app/Con

Problem Description: ipa trial, get feedback from Apple ITMS-90620: Invalid iMessage App - Your iMessage app contains an invalid sticker pack. The app may have been built or signed with non-compliant or prerelease tools. For more information, go to developer.apple.com. Since we added sticker (Messages Application Extension) we checked There is no problem with bundleid of ipa and bundleid of sticker We found that hxl.xcarchive contains the MessagesApplicationExtensionSupport folder, and there is a file named MessagesApplicationExtensionStub in it But we did not include the MessagesApplicationExtensionSupport folder after exporting ipa from hxl.xcarchive Our command line to export ipa is: xcodebuild -exportArchive -archivePath build/20230203_130051/hxl.xcarchive -exportPath build/20230203_130051/ -exportOptionsPlist ExportOptions.plist

Hi, When submitting manually signed macOS apps then this warning is shown after submission: WARNING ITMS-90889: Cannot be used with TestFlight because the bundle at is missing a provisioning profile. Main bundles are expected to have provisioning profiles in order to be eligible for TestFlight. I use the following commands for signing the app: export VM_CERTIFICATE=Apple Distribution codesign --deep -f -s $VM_CERTIFICATE -v --entitlements $VM_SOURCE_PATH/macos/App.entitlements $VM_APPNAME productbuild --component $VM_APPNAME /Applications --sign 3rd Party Mac Developer Installer: MyCompany outmac.pkg How can I get rid of the warning, so that the package can be used in TestFlight? Regards,

I built and submitted a react-native app using expo eas build -p ios --auto-submit and the app was sent to Apple for submission. I received an email back 5 minutes later that reads: Dear Developer, We identified one or more issues with a recent delivery for your app, react-chipsapp 0.1.2 (0.1.2). Please correct the following issues, then upload again. ITMS-90748: ${message} Best regards, The App Store Team The ${message} looks like a template placeholder that isn't populated and thus there is no information indicating what might be wrong. I google searched for the specific error code and could not find anything. What does this code mean and why is my app submission failing?

We received this error after submitting to apple connect today. How can we resolve this issue? Dear Developer, We identified one or more issues with a recent delivery for your app, ****** 1.14 (33). Please correct the following issues, then upload again. ITMS-90338: Non-public API usage - The app references non-public selectors in ErgoAuditor: isKeyDown, modifiedInput, _modifierFlags. 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/ Best regards, The App Store Team

When I go to upload my app to iTunes (like I've done successfully before), it now gives me an ERROR ITMS-90023: Missing required icon file. The bundle does not contain an app icon for iPad of exactly '76x76' pixels, in .png format for iOS versions >= 7.0.However, the icon file IS there, and the reference to it in plist appears to be correct. What am I missing? What should I check, in what order? I'm not a native Mac user. I'm a windows developer, using Cordova to build mobile apps. I only use the Mac for Apple deployments.On a secondary rant... I can put out an Android AND website release in 5 minutes, but end up spending HOURS on the Apple deployments. Why can't Apple just scale the icon by default and allow overrides for specific resolutions? I'm sure we can find a college freshman to explain image scaling to them. This requiring dozens of icon files is ridiculous. I'm now on my 2nd DAY of trying to fix the Apple deploy. Somebody help!-- one very frustrated developer

We received this error after submitting to apple connect today. How can we found these Non-Public API. Thanks for your help. Dear Developer, We identified one or more issues with a recent delivery for your app, ******** 1.7.3 (73). Please correct the following issues, then upload again. ITMS-90338: Non-public API usage - The app contains one or more corrupted binaries. Rebuild the app and resubmit.. 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/ Best regards, The App Store Team

Using Flutter ... has anyone seen these app-store errors: ITMS-90036: This bundle is invalid - The Info.plist file for /Payload/Runner.app/Frameworks/App.framework/flutter_assets/packages/st_ui_builder/build/ios/Debug-iphonesimulator/App.framework is missing or could not be read. ITMS-90207: Invalid Bundle - The bundle at '/Payload/Runner.app/Frameworks/App.framework/flutter_assets/packages/st_ui_builder/build/ios/Debug-iphonesimulator/App.framework' does not contain a bundle executable. The IPA validates just fine on my local M1. I only get these errors after upload to Apple and I can’t find the problem with my build-pipeline

When I try to create a TestFlight build of my app using Xcode Cloud, I get a couple of ITMS-90334 errors and the build fails. The error messages look like: ITMS-90334: Invalid Code Signature Identifier - The identifier 'MySwiftPackage-55554944e95A2da4fe9e3357b44de57c3ba890e8' in your code signature for 'MySwiftPackage_-658550CFFF128C8B_PackageProduct' must match its Bundle Identifier 'MySwiftPackage' Where MySwiftPackage is a Swift Package which is used by a framework as well as the application. The dependencies look like this: MyApp + MyFramework + MySwiftPackage + MySwiftPackage MyApp is a macOS app MyFramework is a mixed Swift and Objective-C framework MyApp is also mixed Swift and Objective-C When I run an archive build on my local Mac and upload the build to App Store Connect to be used as a TestFlight build, everything seams to be fine and the build is accepted I found some discussions on ITMS-90334 but not related to using Swift Packages and Frameworks Any ideas what might be