Search results for

ITMS-90158

1,681 results found

Post

Replies

Boosts

Views

Activity

ERROR ITMS-90534 while uploading an AdHoc build
I've just renewed my mebership yesterday, and I had to create a new Certificate and Provisioning profile for this app I'm developping. I just tried submitting a new AdHoc version (for TestFlight testing), and I've been getting this error:ERROR ITMS-90534: Invalid Toolchain. New apps and app updates must be built with the public (GM) versions of Xcode 6 or later, macOS, and iOS SDK or later. Don't submit apps built with beta software including beta macOS builds.I'm running MacOS 10.12.2 Beta, XCode 8.3 beta 3I've submitted more than 5 AdHoc builds previously on the same OS version and XCode 8.3 beta 1I've read on some other threads that this could be a potential bug on Apple's side, and has to do with some server/OS whitelisting they need to do.But any deterministic answer is fully welcome here! Maybe someone else is also facing this issue ?!
2
0
1k
Mar ’17
ITMS-90338: Non-public API usage
Hello, im receiving this error after submitting our app to Apple Connnect. I've tried changing build configuration to Release in Xcode but still giving me same response from Apple Developer Thank you for any help Dear Developer, We identified one or more issues with a recent delivery for your app, ********* 1.6.0 (20). Please correct the following issues, then upload again. ITMS-90338: Non-public API usage - The app references non-public selectors in ********: _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
0
0
798
Jun ’23
ITMS-90338: Non-public API usage
Backend is automatically refusing app uploads to app store connect. In the refusal email no API is mentioned which is being used. Dear Developer, We identified one or more issues with a recent delivery for your app, Perma Evidence Pro 1.0 (1). 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
0
0
413
Jul ’22
ITMS-90338: Non-public API usage
I am working on a multi-targeted React Native app. I have deployed most of them without any issues. I didn't receive any errors during the process. One of the apps was even validated and uploaded successfully. However, I later received an error message from the Play Store, which is shown below. ITMS-90338: Non-public API usage - The app references non-public selectors in ETCiso: _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 All the settings are the same as the other apps. If there is an error or issue in the binary, then why is it passing validation and uploading successfully? Any one help me to solve this
0
0
159
Jul ’25
ITMS-90809 even though not using UIWebView
Have submitte4d a build to Apple (for TestFlight) and receioved a warning back...ITMS-90809: Deprecated API Usage - Apple will stop accepting submissions of app updates that use UIWebView APIs starting from December 2020I do not use UIWebView - I used to, a long time ago, but changed to WebKit and WKWebView many versions ago.Curious why they detected UIWebView in my App.Anybody else had the same issue recently>(By the way, have submitted numerous builds in the recent past and never received this feedback before)
5
0
4.2k
Apr ’20
ITMS-90078: Missing Push Notification Entitlement
Hi, Our project utilizes push notifications via OneSignal SDK. Everything looks correct and conforms with the documentation: The Push Notifications capability is enabled in XCode. The entitlements do contain the aps-environment key with the production value. I unpacked the resulting IPA and explored embedded.mobileprovision file - it does contain the aps-environment key with the production value in the Entitlements section too. The App ID and provision profiles used do include the Push Notification capability. So there's literally nothing to fix. Despite of that, when uploading the IPA to AppStore Connect, we receive an email with the warning ITMS-90078: Missing Push Notification Entitlement... that says there's no aps-environment entry. Moreover, the OneSignal dashboard indicates Missing Push Capabilities for all the iOS devices that run our application. Consequently, the push messages are not received. What could be wrong with the IPA and where to look at? Thanks in advance!
2
0
1.8k
Jul ’23
ITMS-90338: Non-public API usage
We received this message after uploading IPA to App Store Connect: Dear Developer, We identified one or more issues with a recent delivery for your app, **** 2.4.1 (4). Please correct the following issues, then upload again. ITMS-90338: Non-public API usage - The app references non-public selectors in Onay: _setWidth:. 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 We tried to rename all methods or delete them and republish, but always receive this message. Can we get more detailed error description?
1
0
966
Feb ’23
ITMS-90428: Invalid Swift Suppor
I am trying to upload a new build of my app from the new Xcode 15.0.1 but it keeps failing with the below error: ITMS-90428: Invalid Swift Support - The files libswiftMetal.dylib, libswiftCoreGraphics.dylib, libswiftCoreLocation.dylib, libswiftObjectiveC.dylib, libswiftCoreAudio.dylib, libswiftos.dylib, libswiftDarwin.dylib, libswiftsimd.dylib, libswiftFoundation.dylib, libswiftCoreImage.dylib, libswiftQuartzCore.dylib, libswiftNetwork.dylib, libswiftUIKit.dylib, libswiftCoreFoundation.dylib, libswiftCoreMedia.dylib, libswiftCore.dylib, libswiftDispatch.dylib, libswiftAVFoundation.dylib don’t match /Payload/goodville.app/Frameworks/libswiftMetal.dylib, /Payload/goodville.app/Frameworks/libswiftCoreGraphics.dylib, /Payload/goodville.app/Frameworks/libswiftCoreLocation.dylib, /Payload/goodville.app/Frameworks/libswiftObjectiveC.dylib, /Payload/goodville.app/Frameworks/libswiftCoreAudio.dylib, /Payload/goodville.app/Frameworks/libswiftos.dylib, /Payload/goodville.app/Frameworks/libswiftDarwin.dylib, /Pa
2
0
625
Nov ’23
Error ITMS 90022
When putting my IPA file into Application Loader, I get these two error messages. I was able to fix the icons the message was talking about, I just had to resize them, I did so by going into my zip file, was this the correct thing to do?Also, once I have resized them, do I completely need to redo my whole IPA file? And if so how do I do that? I've been using phonegap to develop an iPhone app.Thank you
0
0
428
Jun ’16
ERROR ITMS 90345
When I attempt to upload the app to ITunes Connect from Xcode I receive the following error: Metadata/Info.plist Mismatch. The value for bundle_version in the metadata.xml file does not match the value for CFBundleVersion
5
0
3.0k
Jun ’16
URL Scheme Incorrect Format
I've been publishing an app on the App Store using the Adobe DPS service for the past few years. I've now just moved onto a new app development software and have started experiencing errors upon uploading a new app to update the previous one on the App Store.After checking everything is correct on the new app development software (Twixl Publisher), I receive this error when uploading my build via Application Loader:ERROR ITMS-90158: The following URL schemes found in your app are not in the correct format: [.co.uk.websitename.websitename]. URL schemes need to begin with an alphabetic character, and be comprised of alphanumeric characters, the period, the hyphen or the plus sign only. Please see RFC1738 for more detail.My Bundle ID in iTunes Connect is: .co.uk.websitename.websitename and has always worked perfectly before. Now it's causing problems and I can't figure out how to fix it so I can update the app with the version.Could anyone advise on the next steps I should take to resolve this issue?Tha
0
0
4.3k
Aug ’16
Assistance Needed: App Submission Issue (ITMS-90426)
Hello, We submitted our app on TestFlight, but received an automated response with the following error: ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it. Our app is developed entirely in Objective-C, and we’re unsure why it’s looking for SwiftSupport. Despite attempting several potential solutions, the error persists. Could someone please assist us with understanding why this is happening and advise on how to proceed with the submission? Any guidance would be greatly appreciated. Thank you for your help.
1
0
492
Jan ’25
ERROR ITMS-90334: Invalid Code Signature Identifier. 
I get this error when trying to submit a beta build. App Store Connect Operation Error ERROR ITMS-90334: Invalid Code Signature Identifier. The identifier com.apple.WK in your code signature for app name watch must match its Bundle Identifier com.appname.watchkitapp I don't know of anything that has changed with the code signing since last successful submission, can't find com.apple.WK anywhere in my project and have tried submitting a previous version with no changes and get the same error. Anyone have any idea what I could be doing wrong?
14
0
4.8k
Oct ’20
Qt - CFBundleExecutable issue: ERROR ITMS-90260
Our application is written in Qt. When uploading the signed PKG-file with Application Loader 3.0 we get the following message:ERROR ITMS-90260: Bad Bundle Executable. You must include a valid CFBundleExecutable key in the nested bundleWe added this string in the info.plist<key>CFBundleExecutable</key> <string>QtCore</string>Tis is what the Mac Developer Library is telling us:For frameworks, the value of this key is required to be the same as the framework name, minus the .framework extension. If the keys are not the same, the target system may incur some launch-performance penalties. The value should not include any extension on the name.But the error message still appears. What is to do? Are there any Qt-apps in the App store?
0
0
582
Mar ’16
ITMS-91054: Invalid API category declaration
I added Privacy manifest for my app and submit it to review and apple reject my app with what comment ITMS-91054: Invalid API category declaration - The PrivacyInfo.xcprivacy for the “Frameworks/SmartlookAnalytics.framework/SmartlookAnalytics” file contains “Disk Space” as the value for a NSPrivacyAccessedAPIType key, which is invalid. Values for NSPrivacyAccessedAPIType keys in any privacy manifest must be valid API categories. For more details about this policy, including a list of required reason APIs and approved reasons for usage, visit: https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api. i look at the package manifest and all looks fine (attached image). Maybe somebody saw that issue - and may tell me how can i fix it.
3
0
2.2k
May ’24