Search results for

ITMS-90158

1,686 results found

Post

Replies

Boosts

Views

Activity

Can't upload new update(ITMS-90109)
Hello. I developed an Unity app for iPhone and iPad, but uploaded only iPhone version. After a while of uploading new updates I can't upload new version of my App with iPad comparability. I have tried to add to graphics API Metal and OpenGLES3, but since start of development I used OpenGLES2 only. Both variants (using OpenGLES2 only or three of kind) return same issue as above.
0
0
495
Oct ’20
ITMS-90338 over LLVM container Usage
We use some of LLVM's containers in our code...llvm/ADT/SmallVector.h for example. When trying to submit our app to the App Store, it gets rejected with:ITMS-90338: Non-public API usage - The app references non-public symbols in X-Plane: __ZN4llvm24DisableABIBreakingChecksE. 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/What gives, Apple? Are we not allowed to use open source code in our app? 😕Is there a way around this without having to search/replace every symbol that Apple's validator finds?
2
0
1.3k
Aug ’19
ERROR ITMS-90512 "Invalid SDK Value"
Suddenly iTunes Connect is rejecting an app which was working yesterday.The error is happening at upload time. Not at compile time. The cause appears to be iOS10 frameworks. Invalid sdk value. The value provided for the sdk portion of LC_VERSION_MIN_TVOS ... is 10.0 which is greater than the maximum allowed of 9.2Finding myself unable to distribute builds from XCode8And unable to distribute builds from XCode7
2
0
1.1k
Jun ’16
ITMS-90338: Non-public API usage
We just compiled and uploaded new release with Xcode 16.1 to the App Store. A few minutes later the following email arrived: The app references non-public selectors in {app_name}: setNavigationBar:. 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. But we don’t have any setNavigationBar methods in our project. Only setNavigationBarHidden calls for navigationController. And this is not private API of course. Please let us know how to upload our update for review. Thank you!
1
0
374
Nov ’24
Reply to Two errors -- binary not optimized for iphone 5 (error 90096) and invalid code signing (error 90163) when submitting to iTunes
The ERROR ITMS- 90096: “Your binary is not optimized for iPhone 5 ……” is SOLVED! I had my splash images in a folder. Once I took them out of the folder and put them in the same directory as the project I was didn't receive the error anymore. The problem for the ERROR ITMS- 90163: “Invalid Code Signing Entitlements error was that a development AND production provisioning profile was using the same App ID. Once I created and paired a separate app ID for the development and production provisioning profile the problem was solved. PROBLEM SOLVED.
Feb ’16
ERROR ITMS-90470: "Missing Info.plist Value. Your app's Info.plist must contain a string value for the 'CFBundleIcons.CFBundlePrimaryIcon' key."
We are trying to upload tv os new build to app store but its not allow us get submitted. We addedTop Shelf Image - 1920 x 720Top Shelf Image Wide - 2320 x 720We are using xcode 9, tried a lot times by deleting assets and adding new.My error listiTunes Store Operation FailedERROR ITMS-90470: Missing Info.plist Value. Your app's Info.plist must contain a string value for the 'CFBundleIcons.CFBundlePrimaryIcon' key.iTunes Store Operation FailedERROR ITMS-90513: Missing Info.plist Key. Your app's Info.plist must contain the 'TVTopShelfImage.TVTopShelfPrimaryImage' key.iTunes Store Operation FailedERROR ITMS-90513: Missing Info.plist Key. Your app's Info.plist must contain the 'TVTopShelfImage.TVTopShelfPrimaryImageWide' key.
0
0
1.1k
Feb ’18
Reply to Direct link to all my apps in App Store not working in iOS 12
Just to follow-up to my post: Apple responded to my case I opened with them. They confirmed that there is no official documentation regarding the itms-apps URL scheme, and that there is no guarantee about engineering side changes. But they suggested I use the format itms-apps://itunes.apple.com/<store name>/developer/<developer name>/id<id number>. The <store name> is the code that matches the developer's apple ID registration. For the United States, for example, it's us. I confirmed this also works with iOS 12.1.As hacknicity posted, it also works without the <developer name> and the <store name>. I wish Apple would officially document the itms-apps URL scheme since it's very useful for developers to be able to link to all our apps in the App Store directly from within our apps in a supported way, without worrying about Apple breaking the scheme in an iOS update.
Topic: App & System Services SubTopic: Core OS Tags:
Dec ’18
ERROR ITMS-90725: "SDK Version Issue. This app was built with the iOS 12.4 SDK
We have two targets.MCOM and MCOM QA and both are built using iOS 12 SDK.But when we submit the MCOM build to Test Flight, we get following message.We identified one or more issues with a recent delivery for your app, Macy's 8.4.2 (8042.200501.150315). Your delivery was successful, but you may wish to correct the following issues in your next delivery:ITMS-90725: SDK Version Issue - This app update was built with the iOS 12.4 SDK. As of June 30, 2020, updates to apps for iPhone or iPad must be built with the iOS 13 SDK or later.But when we try to upload MCOM QA build to Test Flight, we get different messageERROR ITMS-90725: SDK Version Issue. This app was built with the iOS 12.4 SDK. New apps for iPhone or iPad must be built with the iOS 13 SDK or later. Return status of iTunes Transporter was 1: ERROR ITMS-90725: SDK Version Issue. This app was built with the iOS 12.4 SDK. New apps for iPhone or iPad must be built with the iOS 13 SDK or later.So basically Test Flights assumes our QA apps as
14
0
26k
May ’20
ITMS-90171 When Archiving Caused by MLModel Files
I'm trying to submit an app to the store that contains a bundle of `.mlmodel` files.When I archive the app and upload it to the app store I get a list of errors, one for each `.mlmodel` file that is in the bundle.An example of such an error is:Invalid Bundle Structure - The binary file 'MyApp.app/Frameworks/MyFramework.framework/AIModels.bundle/bot2emb51.o' is not permitted. Your app can’t contain standalone executables or libraries, other than a valid CFBundleExecutable of supported bundles. Refer to the Bundle Programming Guide at https://developer.apple.com/go/?id=bundle-structure for information on the iOS app bundle structure.In this particular case I have a file that's marked for inclusion in the `AIModels` bundle called `bot2emb51.mlmodel`. I'm not sure why the file is being compiled into an object file, I thought it would be copied as an `mlmodel` file.Are there any Xcode settings I need to change, or flags that I can set in the compiled to work around this?
0
0
1k
Aug ’18
WARNING ITMS-90725: SDK Version Issue.
Hi EveryoneI got this warning from Apple:SDK Version Issue - This app was built with the iOS 12.0 SDK. Starting March 2019, all iOS apps submitted to the App Store must be built with the iOS 12.1 SDK or later, included in Xcode 10.1 or later. After you’ve corrected the issues, you can use Xcode or Application Loader to upload a new binary to iTunes Connect.I updated my xcode to the latest 10.1 version and my Application Loader is Version 3.7.2. I developed a new build after updating but I am still getting the SDK Version Issue. Is anybody else having this problem and do you know how to resolve it?Kind RegardsDaniella
4
0
6.1k
Jan ’19