Search results for

ITMS-90158

1,686 results found

Post

Replies

Boosts

Views

Activity

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
898
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.8k
Nov ’22
ITMS-90338: Non-public API usage
ITMS-90338: Non-public API usage - The app references non-public selectors in SMMplanner: _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/
1
0
536
Nov ’22
ERROR ITMS-90680: "Invalid directory. The bundle (...)StickerPackExtension.appex is not contained in a correctly named directory. It should be under "PlugIns".
Using XCode 10.2.1Submitting my first stickers app for iOS for testing.When uploading archive to itunesconnect I'm now getting this error:ERROR ITMS-90680: Invalid directory. The bundle Payload/App Name.app/App Name StickerPackExtension.appex is not contained in a correctly named directory. It should be under PlugIns.My project structure is now:App Name - Stickers.xcstickers - Products - App Name.app - App Name StickerPackExtension.appexI don't see any way to move .appex to a PlugIns folder (non existing) as the error suggests.Additionally the project structure is the default structure I'm getting when creating Sticker Pack Appin Xcode.So I'm not sure why is the process complaining about the .appex being in a wrong directory and I have no idea how to fix this to proceed further.Any help appreciated!
1
0
2.0k
Nov ’22
ITMS-90053, ITMS-90055, ITMS-90345 Error when trying to archive a duplicated app
Hi, I am creating a workflow in Xcode Cloud for a duplicated react-native application. I have changed the bundle identifier and created a new application in App Center with the same bundle identifier. in cloud when I am trying to proceed with the step Archive-IOS it throws following errors, but those are not thrown in Build-IOS step. Please provide me some suggestions. Error details: ITMS-90053: This bundle is invalid - The bundle identifier is already in use by a different software package. ITMS-90055: This bundle is invalid - The bundle identifier cannot be changed from the current value, '(duplicated.app.build.identifier)'. If you want to change your bundle identifier, you will need to create a new application in App Store Connect. ITMS-90345: Metadata/Info.plist Mismatch - The value for bundle_identifier in the metadata.xml file does not match the value for CFBundleIdentifier in (Old App Name) [Payload/(oldappName)].
2
0
2.2k
Nov ’22
ITMS-90334: Invalid Code Signature Identifier
I get the following error in Xcode Cloud when attempting to prepare a build for App Store: ITMS-90334: Invalid Code Signature Identifier. The identifier SwiftCharts-555549449cfa473253483215b74c174849d2ec9c in your code signature for SwiftCharts must match its Bundle Identifier SwiftCharts. This is an iOS app and Swift Charts is swift package dependency which the app depends on. Since it is a dynamic library, it is included via the Embed & Sign option. This was reported on SO by another user. They worked around it by making changes to the source package, I believe. That workaround may be difficult in my case as I do not control the source package. It's a 3rd party dependency that I'd prefer not to maintain a fork of. Any ideas of why Xcode cloud is hitting this issue or any other workarounds? I've confirmed via a codesign check that the Identifier is resolving to that special hash when doing this from Xcode Cloud. It does not have that hash when I attempt to build/archive/upload locally. $ codesig
2
0
1.2k
Oct ’22
Using XCode 13.3.1 and SDK 15 but build won't load through Transporter App and error email says : ITMS-90725: SDK Version Issue - This app was built with the iOS 14.4 SDK. All iOS apps submitted to the App Store must be built with the iOS 15 SDK
Hi, I am trying to upload a mobile game I created for iOS app store for beta testing with friends and family through testflight. I have especially purchased a MacBook Pro running XCode 13.3.1 and Monterey 12.3.1 and an iPhone running Software version 15.4.1 to this end. My XCode deployment target is set to iOS 15.4 and my Unreal Engine 5.01 minimum iOS version in packaging is set to 15. As far as I can tell everything is set to be as up to date version wise as possible, yet every time I try uploading the packaged game through transporter app the build won't show up in App Store Connect and I get an error email from the development team saying : ITMS-90725: SDK Version Issue - This app was built with the iOS 14.4 SDK. All iOS apps submitted to the App Store must be built with the iOS 15 SDK or later, included in Xcode 13 or later. Now I've emailed the team and their response was to version up and try again and look for the error in the email. So I did that and got the exact same error and no build ava
4
0
6.3k
Oct ’22
Codesign and AppStore verification failure after manually lipo'ing two dylibs
We are creating a universal build of our application for the Mac App Store by merging separate x86_64 and arm64 bundles using a script. Codesign verification fails for some dylibs if they are signed after merging: % lipo -create x86_64/test.dylib arm64/test.dylib -o universal/test.dylib % codesign -s *** -f --timestamp universal/test.dylib % codesign --verify --verbose=2 universal/test.dylib test.dylib: invalid Info.plist (plist or signature have been modified) It seems verification fails for only those dylibs that have an Info.plist embedded in them. We were able to work around this issue by signing the individual dylibs before merging, but now AppStore verification is failing with the following error: ITMS-90336: Mismatched Embedded Info.plist: The executable 'test.dylib' has mismatched embedded Info.plists. This could be due to the use of 3rd party build tools. Does this mean that the __info_plist section in all the slices in the universal binary should be exactly the same (bitwise)? Some of these
3
0
2.0k
Oct ’22
Endpoint Security Extension + SandBox + App Distribution
Hi All, I'm developing a security application that uses an endpoint security extension. The application has two parts main and extension. I have an entitlements for Security Extension Client from Apple. I'd like to distribute apps through the Apple Store. Locally the app runs without problems on enabled machines, but when I try to get it through Testfligt to the appstore I get two errors: ITMS-90285 - Invalid Code Signing Etitlements. Your application bundle’s signature contains code signing etitlements that are not supported on MacOs. Specifically, key ‚com.apple.developer.endpoint-security.client‘ ITMS-90296 - App sandbox not enabled on extension When I turn on sandbox for extension, the extension fails to register endpoint security client let res = es_new_client(&client) { _, event in self.eventDispatcher(msg: event) Without sandbox it runs without any problem. Thank you very much for your help I don't know how to proceed. Martin
4
0
1.8k
Oct ’22