ITMS-90158

Hello, I'm trying to submit an app to apple connect that is build outside of xcode but I'm getting this email saying the files have an invalid signature. I'm doing a step wrong or maybe using the wrong signature but not sure what is supposed to be the way to do it. The app is written with python and pyside, and packaged with pyinstaller. In the pyinstaller .spec file I set the codesign_identity and entitlements_file and also fill some things to the info_plist (CFBundleVersion, LSApplicationCategoryType, etc). This results in a .app file, which then I run a command on it: productbuild --component path/to/file.app /Applications path/to/file.pkg --sign And then push with: xcrun altool --upload-app path/to/file.pkg --type macos -u -p I'm able to upload but then I get the email with the signature error (ITMS-90238: Invalid Signature). Are these steps ok, or something else is needed?

I received an email with the following message from Apple: ITMS-90725: SDK Version Issue - This app was built with the iOS 15.5 SDK. All iOS apps submitted to the App Store must be built with the iOS 15 SDK or later, included in Xcode 13 or later. Well, what's the problem Apple? I used 15.5. That's later than 15!

HiSorry, my english is bad!A few weeks ago, I sent an app of stickers to AppStore. Now I'm trying to do an update making it a standard app with an extension of stickers.When I try to upload, App Loader displays the following message:ITMS-90639 ERROR: Invalid Binary The value of LSApplicationLaunchProhibited in Payload / PicMessage.app / Info.plist can not change after your app has been released..I have tried many things, such as recreating the Xcode project from scratch. Also I put LSApplicationLaunchProhibited true (and then receive other types of errors). Nothing solves my problem.How can I solve this problem?Regards,Angel

I built and submitted a react-native app 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, TYPSA REGISTRO DE JORNADA 1.0.2 (1.4). 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?

ERROR ITMS-90347: Bad bundle identifier. The bundle identifier 'com.legacylouisvillellc.legacylouisville' of the application extension Legacy Louisville.app/PlugIns/OneSignalNotificationServiceExtension.appex should start with the application's bundle identifier 'com.legacylouisvillellc.legacylouisville' and not contain more than one period “.” after the application's bundle ID. ERROR ITMS-90685: CFBundleIdentifier Collision. There is more than one bundle with the CFBundleIdentifier value 'com.legacylouisvillellc.legacylouisville' under the iOS application 'Legacy Louisville.app'. Hello, each time I am trying to upload this to the App Store for submission, I can't avoid these two error codes. Can anyone assist me? Thank you so much... Dave

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