Search results for

ITMS-90158

1,681 results found

Post

Replies

Boosts

Views

Activity

ITMS-90338: Non-public API usage
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
22
0
7.3k
Dec ’22
ITMS-90036 & ITMS-90207 errors
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
1
0
1k
Dec ’22
Reply to ITMS-90334 error when executing a Xcode Cloud TestFlight build
macOS 13.1 beta 4 addresses the issue creating ITMS-90334: Invalid Code Signature Identifier in Xcode Cloud. No update to Xcode is necessary to address the issue. This beta was released yesterday, and is available in Xcode Cloud when you configure a workflow to specify the macOS version used to execute your build. As this version is currently a beta, it is only available as part of the Latest Beta or Release macOS configuration, or as a dedicated choice for the macOS version, at this time. If you find this issue is not addressed with this configuration change to your Xcode Cloud workflow, continue to provide us feedback through Feedback Assistant, and share the FB numbers here so I can follow up on them.
Dec ’22
ITMS-90334 error when executing a Xcode Cloud TestFlight build
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
6
0
3.3k
Dec ’22
when i upload the ios app i got the error "ERROR ITMS-90086: Missing 64-bit support. Beginning on February 1, 2015 new iOS apps submitted to the App Store must include 64-bit support and be built with the iOS 8 SDK. Beginning June 1, 2015 app updates will
when i upload the ios app i got the error ERROR ITMS-90086: Missing 64-bit support. Beginning on February 1, 2015 new iOS apps submitted to the App Store must include 64-bit support and be built with the iOS 8 SDK. Beginning June 1, 2015 app updates will also need to follow the same requirements. To enable 64-bit in your project, we recommend using the default Xcode build setting of “Standard architectures” to build a single binary with both 32-bit and 64-bit code. how to solve it?
2
0
3.4k
Dec ’22
Getting Invalid GeoJson on submitting app
On repetitive attempts, I am getting Invalid Binary with ITMS-90117: Missing routing app coverage file: You must upload a routing app coverage file in App Store Connect if you register as a routing app. Here is my Geo Json file: { type: MultiPolygon, coordinates: [ [[[-141.1,43.7], [-141.1,69.7], [-52.3,69.7], [-52.3,43.7], [-141.1,43.7]]], [[[-127.2,22.9], [-127.2,49.4], [-58.5,49.4], [-58.5,22.9], [-127.2,22.9]]], [[[2.2,49.3], [2.2,51.3], [6.5,51.3], [6.5,49.3], [2.2,49.3]]], [[[59.0625,4.915832801313164], [100.546875,4.915832801313164], [100.546875,38.8225909761771], [59.0625,38.8225909761771], [59.0625,4.915832801313164]]] ] } I just include 3 countries - USA, Canada and India, as I selected these 3 countries AppStore to list my app. Can you please help me what is wrong with the above file? I don't get any error and there is no way to debug this. Thanks
4
0
3.2k
Nov ’22
Cant upload to TestFlight, ITMS-90338: Non-public API usage
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
3
0
813
Nov ’22
ITMS-90338: Non-public API usage no specific reason
Hi, Received a message from apple regarding my app delivery. ITMS-90338: Non-public API usage - The app contains one or more corrupted binaries. Rebuild the app and resubmit.,The app contains one or more corrupted binaries. Rebuild the app and resubmit.,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/ Ran build and analyze no issues found Also did a Validate archive before submitting
6
0
3.1k
Nov ’22
ITMS-90338: No corrupted binaries listed
ReDeploying an App today after a deployment yesterday. No changes to the build. Receiving this error message below, however no binaries are listed as corrupted in the error message.. 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. Any help would be appreciated.
8
0
2.2k
Jul ’22
ITMS-90338: Non-public API usage
We started receiving this error a few days ago when it appeared to be a wide spread problem on Apple's end. https://developer.apple.com/forums/thread/127678?answerId=715975022#715975022 Although it is supposedly resolved, I am still getting this error. I have incremented build and version numbers along with tweaking code. Also, the build agent is running macOS 12.4 and Xcode 13.4.1. ITMS-90338: Non-public API usage - The app contains one or more corrupted binaries. Rebuild the app and resubmit.,The app references non-public selectors in Align-Dev: isActivated. 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/ The only
4
0
3.0k
Nov ’22
ITMS-90338: Non-public API usage
The below-mentioned points I received in a mail from the App Store, when I tried to upload the build to the App Store. Though I didn't found any such keywords when I searched in my code. Please help with this. Thank you. ITMS-90338: Non-public API usage - The app references non-public symbols in ClikSource: kPOPLayerOpacity, kPOPLayerScaleXY. 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. ITMS-90827: Invalid character in a UTI - The CFBundleDocumentTypes dictionary array in the 'com.cliksource.employer' contains a CFBundleTypeName whose LSItemContentTypes has an element that contains the character '/' or ':', which are not allowed.
1
0
1.9k
Nov ’22
ITMS-90338: Non-public API usage
Dear Developer, We identified one or more issues with a recent delivery for your app Please correct the following issues, then upload again. ITMS-90338: Non-public API usage - The app references non-public symbols in Loupe: _CGImageGetImageSource. 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 There are two problems, one is that our release/production build is succeeding and uploading to TestFlight. The other problem is we do not understand what the issue is even when reading your automatic message. How can we debug this ? How can we identify the source of the problem ? Do you have a
6
0
893
Nov ’22
ITMS-90625 Error on App Store Connect with Siri Intents
I'm trying to get an update for one of my apps submitted but I'm running into problems when trying to distribute the app. The App Store Connect service goes through all the steps of uploading the binary and then fails at the very end with a triple error ITMS-90625: Invalid Intent Extension. The NSExtensionAttributes key in the Info.plist file can't contain the intent name INCurrentRateIntent. I tried to fix the error, tried to look for others with the error, but so far I have drawn a blank.This is an overview of the structure of the app. The app has an iOS/iPadOS target as well as a WatchOS target. The app is written in Swift/SwiftUI with minimal UIKit hooks and targets iOS 13.2. In addition, there is a widget target. The WatchOS app is a standalone app. All of these components work well and are the current version of the app as available on the App Store.For the next app update I want to add support for Siri Intents. I did so by adding a new iOS Siri intents target (there are no intents for the Watc
7
0
2.4k
Nov ’22
ITMS-90476 - Invalid Bundle (LaunchScreen error)
I have an issue that has prevented me from releasing two of my new apps so far. I created two new SwiftUI projects in Xcode 12 since WWDC20, both built with SwiftUI. By default these don’t include a LaunchScreen.storyboard, as you can now set the Launch Image in the info.plist. That was too fiddly and I didn’t like it, so I added a LaunchScreen.storyboard to my bundle, set it up, and set the Launch screen interface file base name value in my info.plist. The launch screen looks and works great when testing on my devices and simulators. However, when trying to upload to App Store Connect, I get the following error: ERROR ITMS-90476: Invalid Bundle. Your app supports multitasking on iPad, so you must include the launch storyboard file, 'LaunchScreen.storyboard', in your bundle, 'com.companyname.appname.' I’ve searched online several times, but all the answers just say ‘Check the Requires Full Screen box on your target’ - completely unhelpful as I want to support multitasking, and as of April 2020 multit
2
0
4.7k
Nov ’22