Search results for

ITMS-90158

1,681 results found

Post

Replies

Boosts

Views

Activity

ITMS-90035 - Invalid Signature. Code object is not signed at all (XCode 7)
After upgrading to XCode 7 (and iOS 9 SDK/ Swift 2.0) I can't submit apps to iTunes connect anymore. I keep getting the response: ITMS-90035 - Invalid Signature. Code object is not signed at all.I already checkt that my provisioning files are up to date, valid and ready for deployment. I also checkt my targets for beeing release builds (as suggested in the error).Any experiences with this issue?PS: I'm using GoogleAnalytics and AdMob Framework but already tried different versions - still getting rejected! According to StackOverFlow this might be caused by .sh files or files that start with '#!' - but I can't find any of these in my project.
2
0
1.5k
Jul ’15
APPLICATION LOADER: Error itms 90168 binary was invalid
Since 3 weeks ago we are unable to submit our apps on the app store with application loader.I've tried to reinstall application loader, update it from 3.0 to 3.1, regenerate our IPA (we're using phonegap builder).I've tried with old version of macbook and osx, to... i'll going crazy! Any ideas? [2016-11-07 17:49:42 CET] <main> INFO: Transporter is searching for updated software components. [2016-11-07 17:49:43 CET] <main> INFO: Transporter is up-to-date. [2016-11-07 17:49:44 CET] <main> INFO: MD5 checksum calculation in the transporter will be skipped. [2016-11-07 17:49:44 CET] <main> INFO: Logging level set to eXtreme [2016-11-07 17:49:44 CET] <main> INFO: Logging configured successfully. [2016-11-07 17:49:44 CET] <main> DEBUG: Attempting refresh of configuration data from https://contentdelivery.itunes.apple.com/transporter/Defaults.properties [2016-11-07 17:49:44 CET] <main> DEBUG: Configuration refresh successful. [2016-11-07 17:49:44 CET] <main> DEBUG: Savi
0
0
1.1k
Nov ’16
Submitting 2 apps with the same framework => 1 passes, 1 has ITMS-91065 error
Hi, I manage apps for several clients. I have 2 apps for 2 different clients in which I use OneSignal version 5.1.5 (https://github.com/OneSignal/OneSignal-XCFramework). The OneSignal part of these 2 applications are configured identically. For both applications I can Build the project Create an archive of the project Send the archive to TestFlight Install the TestFlight version on an iPhone Launch the app on the iPhone For the 1st application I can submit to AppStore it without any problem. For the 2nd application when I submit to AppStore it I have the error ITMS-91065 almost immediately in return by email. ITMS-91065: Missing signature - Your app includes “Frameworks/OneSignalCore.framework/OneSignalCore”, which includes OneSignalCore, an SDK that was identified in the documentation as a privacy-impacting third-party SDK. If a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a signature file. Please contact the provider of t
1
0
922
Aug ’24
Reply to The value for the key 'MinimumOSVersion' in bundle [notification extrension] is invalid. The minimum value is 10
Hi @Hiren Gujarati, Did you figure out a solution to ITMS-90736 error? I'm recently adding iOS 14 configurable widget with its WidgetIntent. Since the new API requires iOS 14, I must set the new target for WidgetIntent to deployment target 14.0. However, it's complaining when I submit to App Store with the following error: ERROR ITMS-90736: Invalid Intent Extension. The MinimumOSVersion key in the 'MyApp.app/PlugIns/WidgetIntents.appex' Info.plist file can't be greater than '11.4'. My main app is still supporting 11.4
Sep ’20
Error uploading ResearchKit app to App Store - ERROR ITMS-90035 Invalid signature
I have created an iOS app that uses the ResearchKit framework. I have dragged ResearchKit.xcodeproj to my app project and embedded ResearchKit.framework in my app target, with the option embed & sign. I am using ResearchKit 2.0.0 and Xcode 11.3.1.When I try to upload the archive (release) to the App Store I get the error ERROR ITMS-90035. Invalid signature. Code is not signed at all. The file at path [XXX.app/Frameworks/ResearchKit.framework/plist-to-strings.py] is not properly signed.This file is part of Apple's ResearchKit, and the settings under Signing and Capabilities do not allow me to add a signing certificate - I select Distribution certificate but Xcode leaves the selection as None.My app has my distribution certificate and provisioning file, and I have followed the suggestions in the error message with regards to selecting Clean Build Folder and deleting the build folder from Finder.Has anyone had a similar problem and been able to upload to the App store?
2
0
1k
Feb ’20
Reply to xcodebuild proxy settings
I have not found any right way of doing this, but I have found a working hack. It turns out that xcode is embedding a Java Runtime wich is used for the upload. I replaced the java-executable with my own script that sets the proxy-values for the java process and importing my certificate to the keystore for the java-runtime. Location of the java runtime: /Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/Versions/A/itms/java/bin/java Location of the keystore: /Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/Versions/A/itms/java/lib/security/cacerts The script I replaced the java-exec with (I first renamed the old executable: mv java java.real): #!/bin/bash /Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/Versions/A/itms/java/bin/java.real -Dhttps.proxyHost= $* Remember to make the script executable (chmod a+x java) This is a hack and might very well break in the future, but hopefully
Nov ’20
ITMS-90714: Invalid binary - The app contains one or more corrupted binaries. Please rebuild the app and resubmit.
While uploading the application into the TestFlight the following error received, ITMS-90714: Invalid binary - The app contains one or more corrupted binaries. Please rebuild the app and resubmit. After sometimes generate same configuration the application successfully submitted on the TestFlight. We are using Xcode 15.3
4
0
1.5k
May ’24
App refused by Apple with error ITMS-90338: Non-public API usage
Hi, we were able to migrate our solution from Xamarin to MAUI (.net 8). After a 2 weeks fight, the app is finally working on my dev devices. Unfortunately, after sending the app to review, it gets rejected because of the following: ITMS-90338: Non-public API usage - The app references non-public symbols in [Our app name]: _SCDynamicStoreCreate, _SCDynamicStoreCreateRunLoopSource, _SCDynamicStoreKeyCreateNetworkServiceEntity, _SCDynamicStoreSetNotificationKeys. 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/ From what I understand, this is because the 4 methods (_SCDynamicStoreCreate, _SCDynamicStoreCreateRunLoopSourc
25
0
2.3k
Jun ’24