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

In our IOS app, we have few libraries that do not spport BITCODE so we had ENABLE_BITCODE set to NO for the iOS APP and Yes for the Watch App.And, this setting has worked for us in the past but now we are getting error during submission. ERROR ITMS-90635: Invalid Mach-o formatThe Error descriptions mainly says that all targets for a platform should have a consistent value of ENABLE_BITCODE.Is bitcode now required for iOS Apps too if we have a Watch App?

Hi there.I'm developing a mobile application on both iOS and Android platforms, using Ionic Framework.I make all certificates by following http://docs.ionic.io/docs/ios-build-profiles, they look all good and compilation with Ionic is successful.Then I upload the .ipa file via Application Loader to make it available on TestFilght.The last build was made on march 18th 2016 with no issue, but Application Loader rejects my build today :✖ ERROR ITMS-90034: Missing or invalid signature. The bundle 'com.ionicframework.oenobook841275' at bundle path 'Payload/Oenobook.app' is not signed using an Apple submission certificate.I tried to recreate every certificate (for distribution), they're all green in my keychain and Developer account.I went back on a previous build thanks to Git.I even did format my Mac, so everything I can use is up to date.Help. 😢

I'm trying to upload a version with Compose multiplatform dependencies, and I get an email: 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 symbols in Nanit: _ubidi_close, _ubidi_getDirection, _ubidi_getLength, _ubidi_getLevelAt, _ubidi_openSized, _ubidi_reorderVisual, _ubidi_setPara, _ubrk_clone, _ubrk_current, _ubrk_first, _ubrk_getRuleStatus, _ubrk_getRuleStatusVec, _ubrk_isBoundary, _ubrk_last, _ubrk_next, _ubrk_previous, _uloc_getDefault, _uloc_toLanguageTag, _uscript_getScript. 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. When I run the validation from Xcode it works. Can you please advice?

I have an app that I'm building and signing and deploying for the Mac App Store. I received an email that there were problems with the deployment that make no sense to me. ITMS-90286: Invalid Code Signing Entitlements - Your application bundle's signature contains code signing entitlements that are not supported on macOS. Specifically, value '367****Y2.com.foo.foo-one.electron' for key 'com.apple.application-identifier' in 'Foo One.app/Contents/MacOS/Foo.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Libraries/libEGL.dylib' is not supported. This value should be a string starting with your TEAMID, followed by a dot '.', followed by the bundle identifier . Say what now? This value should be a string starting with your TEAMID, followed by a dot '.', followed by the bundle identifier . But that is exactly what it is set to: 367****Y2.com.foo.foo-one.electron (asterisks just here to obscure our actual TeamID) I have no idea how to proceed. Any advice? Similar to this question thread 6984

I keep getting emails saying my app cant be processed, how can I fix it or find out whats causing it. Dear Developer, We identified one or more issues with a recent delivery for your app, EmbryosIOS 0.1 (0.99). 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

I have been building the app with XCode 13 Beta and submitting the same to TestFlight so that our internal testing team can test it(I am using the Command Line Tools XCode 13.0 (13A5155e). It allowed me to submit several builds to Testflight until this morning. However, it is complaining now that I am using an invalid version. See below ITMS-90534: Invalid Toolchain - Your app was built with an unsupported SDK or version of Xcode. If you plan to submit this build to the App Store, make sure you are using the versions listed in https://help.apple.com/xcode/mac/current/#/devf16aefe3b or later. Since we are using iOS 15 features, I cannot build with XCode 12.x. Your help is appreciated.

I have recently added some Swift files to my Objective C project that I had been successfully publishing to the AppStore. I'm able to debug on my devices and simulators but when submitting to AppStoreConnect I get the following email: Dear Developer, We identified one or more issues with a recent delivery for your app, ...... . Please correct the following issues, then upload again. ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it. Best regards, The App Store Team From the internet I gather the following build settings are required for the project but that doesn't seem to help my case: 1. Defines Module -> YES 2. Always embed Swift Standard libraries -> YES To reproduce the problem, do the following: Create new Objective C project in XCode Add a single Swift file and choose YES when prompted to make the bridging header Set Defines Module and Always embed Swift Standard libraries to YES in buil

I understand that this error is because Organizer is submitting a binary with the same version number, but I have changed the version numbers. I've done the homework and looked up similar forum posts on this error, but the problem is not as simple as incrementing the build number.Here's what I did:My current version in the store is 2.0.4In iTunesConenct, I created a new version submission for 2.1.0. I filled out all fields (except Build) and clicked Save. It is now marked Ready for Submission.In Xcode, I changed the Version to 2.1.0 and the Build to 2.1.0.In Xcode, I built and ran the app. It works!I opened Organizer. In Archives, it shows Version 2.0.4, and my last submission was months ago.In Organizer, I clicked Submit and followed the steps. I got the Redundant Binary error that 2.0.4 already exists.To double-check, I opened my -Info.plist file and it shows both Bundle Version and Bundle Versions string, short as 2.1.0To triple-check, I looked in my Target > Build Settings > Packaging. I can see tha

I have a maccatalyst App on the store, uploaded 20 March. Am now attempting to upload a new version but it fails with:Unable to process application at this time due to the following error: Invalid Provisioning Profile. The provisioning profile included in the bundle maccatalyst.com.plugh.XYZZY [maccatalyst.com.plugh.XYZZY.pkg/Payload/XYZZY.app] is invalid. [Invalid 'com.apple.application-identifier' entitlement value.] For more information, visit the macOS Developer PortalAs I mentioned this App is already on the store and nothing has change in the project relating to profiles/signing to my knowledge other than a new Xcode. In fact, signing and provisioning is all automatic, and the maccatalyst app id is auto-generatedInterestingly, I still have the previous App bundle that was successfully uploaded to the store, and when I (re-)verify it there is an identical error to the above. So I am at a loss as to how to move ahead at this point in time.

Hi, I receive the following mail after the upload of my app form xCode to the Apple Connect platform. Before uploading, I correctly validate the version, and xcode gives me the validation. Do someone know how resolve this issue? Thanks in advance