Search results for

ITMS-90158

1,686 results found

Post

Replies

Boosts

Views

Activity

How to check for ITMS-90284: Invalid Code Signing Errors befor uploading apps to the App Store?
Again we have the massive problem, that one of our Games (a Unreal4 app, not made with xcode and as 3rd party developer) always gets this error when we try to upload it: ITMS-90284: Invalid Code Signing - The executable 'appname.pkg/Payload/appname.app/Contents/MacOS/appname' must be signed with the certificate that is contained in the provisioning profile. - Yes, we had the problems in the past, but these could all be solved. Now it's different. So, after days of research we can not found how to solve it, even after renewing certs etc etc as we did in the past ... Is there any way to check the .pkg file (before sending it many hours to the appstore) to get a valuable message if code signing is now correct? To check the embedded file: security cms -D -i nameofapp.app/Contents/embedded.provisionprofile helps so see the entries, but they are ok. Thanks for help and ideas.
Topic: Code Signing SubTopic: Certificates, Identifiers & Profiles Tags:
1
0
1.2k
Oct ’22
Blank App icon issue Xcode 13
Hi! My app has App Icon set up and it was working perfectly up until about 3 weeks ago. Now I see blank logo on the screen and cannot Submit for Review new builds, because it shows the following errors: ERROR ITMS-90713: Missing info.plist value. A value for the Info.plist key 'CFBundleIconName' is missing in the bundle. ERROR ITMS-90704: Missing App icon. An app icon measuring 1024 by 1024 pixels in PNG format must be included in the Asset Catalog of apps built for IOS... But I have : appIcon set up for all sizes showing no errors App Icon source in Target -> General is chosen as AppIcon 'CFBundleIconName' - 'AppIcon' in info.plist Successfully uploaded app version to App store around 3 weeks ago. I suspect it may have started after I switched to the new build system (which made me remove info.plist from Copy Bundle Resources in Build Phases). Looks like a similar issue to that one https://developer.apple.com/forums/thread/682648 Will be grateful for any help! Xcode Version 13.0 (13A233
Topic: Developer Tools & Services SubTopic: Xcode Tags:
3
0
2.5k
Oct ’22
ITMS-90338: Non-public API usage automatic refuse
Hello, The problem is we do not understand what the issue is even when reading your automatic message. Detail, before updating to version 14 it worked perfectly, so much so that it was deployed to the store. Today it works perfectly on the emulator and on the device, by xcode. How can we debug this ? How can we identify the source of the problem ? Do you have any idea of what the problem is ? Xcode: 14.0.1 macOS: Monterey Pro Chip M1 React Native: 0.69.5
Topic: Developer Tools & Services SubTopic: Xcode Tags:
3
0
418
Oct ’22
Swift Playgrounds for iPad: ITMS-90334: Invalid Code Signature Identifier
ITMS-90334: Invalid Code Signature Identifier - The identifier 'bundle id followed by 30 random characters' in your code signature for 'bundle id' must match its Bundle Identifier 'bundle id' Currently, any app I’ve tried is getting this error when submitting from the app. I’ve got all the places where you put the name, the sku, and bundle id set with the same value (copy/paste), and I’ve tried different variations, but now that long string of random characters is appended and I can’t use TestFlight. Maybe because this is a beta iPad OS? Been on a beta for what seems like forever. It’s worked in the past. Great. Totally innocuous post that has something that is not permitted. Be nice if you TELL me what’s NOT PERMITTED!
Topic: App Store Distribution & Marketing SubTopic: General Tags:
3
0
901
Oct ’22
Xcode Cloud + dynamic library package
I'm trying to archive my app via Xcode Cloud and auto-deploy to TestFlight but it fails during Prepare Build for App Store Connect with the following error message: ITMS-90334: Invalid Code Signature Identifier. The identifier CoreImageExtensions-dynamic-555549444e09e22796a23eadb2704bf219d5c1fa in your code signature for CoreImageExtensions-dynamic must match its Bundle Identifier CoreImageExtensions-dynamic CoreImageExtensions-dynamic is a .dynamic library target of a package that we are using. It seems that at some point a UUID is added to the library's identifier, which messes with code signing. When archiving and uploading the app in Xcode directly, everything works just fine. Any idea why this is happening and how I could fix it?
Topic: Developer Tools & Services SubTopic: Xcode Cloud Tags:
5
0
3.1k
Oct ’22
Reply to ITMS-90334 error when executing a Xcode Cloud TestFlight build
There is an issue with Ad-Hoc signing of dynamic libraries built either through a Swift Package, or through an Xcode target with a non-standard Bundle ID (i.e. one not using reverse DNS format), resulting in the ITMS-90334 error message. We'd appreciate getting reports of this filed through Feedback Assistant, and then posting the FB number here so that I can follow-up on the reports internally. Even if the following workaround information is helpful to you, we'd still appreciate getting the Feedback reports. The best practice for Swift packages is to not explicitly specify the LibraryType in the Product. By not specifying this value, you let Xcode decide the best linkage type for your app's usage of the package. If you have a package that is explicitly marked as dynamic, removing the library type means Xcode will link the package statically if the package is only imported by one target, which will avoid the issue. If the package is imported by more than one target, Xcode will choose dynamic linkage
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Oct ’22
Reply to ERROR ITMS-90334: Invalid Code Signature Identifier. 
Me too, but a simple app using Swift Playgrounds on iPad. I sent a message to support about this describing what I was doing, and a copy of the error and got the response: “We're unable to determine the nature of your request. Please reply to this email with clarification”. This was the error I get back in email: ITMS-90334: Invalid Code Signature Identifier - The identifier 'Johnboxgame-numbers_and_letters_that_forums_thinks_are_offensive' in your code signature for 'Johnboxgame' must match its Bundle Identifier 'Johnboxgame' WIth the iPad app there’s not really much I can control as far as what goes in the bundle, and it’s worked in the past.
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
Oct ’22
ITMS-90338: Non-public API usage and ITMS-90426: Invalid Swift Support in Expo
Hello, I tried to push a build to TestFlight and received these two errors a few weeks ago. Dear Developer, We identified one or more issues with a recent delivery for your app, App Name. Please correct the following issues, then upload again. ITMS-90338: Non-public API usage - The app references non-public selectors in : _isKeyDown, _modifiedInput, _modifierFlags, determineAppInstallationAttributionWithCompletionHandler:, handleNotification:, isPassthrough, lookupAdConversionDetails:, onSuccess:, removeValuesForKeys:completion:, transform:, viewManager. 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/ ITMS-9
Topic: App Store Distribution & Marketing SubTopic: TestFlight Tags:
3
0
1.5k
Sep ’22
ITMS-90683: Missing Purpose String in Info.plist, but NSUserTrackingUsageDescription is set in InfoPlist.strings
Hello, when uploading a build to AppStoreConnect we got this issue: ITMS-90683: Missing Purpose String in Info.plist - Your app‘s code references one or more APIs that access sensitive user data. The app‘s Info.plist file should contain a NSUserTrackingUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. If you're using external libraries or SDKs, they may reference APIs that require a purpose string. While your app might not use these APIs, a purpose string is still required. For details, visit: https://developer.apple.com/documentation/uikit/protecting_the_user_s_privacy/requesting_access_to_protected_resources Its correct that we don't have NSUserTrackingUsageDescription but it is set in InfoPlist.strings and our QA verified it is working for all supported languages. Do we need to add NSUserTrackingUsageDescription to the plist, but then its not localised? Or is there some ghost language that is not being set correctly (i.e. en-US, e
Topic: Accessibility & Inclusion SubTopic: General Tags:
2
0
2.6k
Sep ’22
TMS-90338: Non-public API usage - The app references non-public selectors
Dear Developer, We identified one or more issues with a recent delivery for your app, COMLAB 101.0.0 (7.0.0). Please correct the following issues, then upload again. TMS-90338: Non-public API usage - The app references non-public selectors in Comlab: _isKeyDown, _modifiedInput, _modifierFlags, handleNotification:, invalidateInputAccessoryView, isPassthrough, onSuccess:, removeValuesForKeys:completion:, updateSettings:, viewManager. 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/ Though you are not required to fix the following issues, we wanted to make you aware of them: ITMS-90683: Missing Purpose String in Info.pli
Topic: App Store Distribution & Marketing SubTopic: App Review Tags:
1
0
687
Sep ’22
Reply to ITMS-90338: Non-public API usage and ITMS-90426: Invalid Swift Support in Expo
Any Update? I also had an issue related to Invalid Swift Support. This was a minor change from a version that passed review a few days earlier, and now the binary is invalid. Our issue was: ITMS-90433: Invalid Swift Support - The file libswift_Concurrency.dylib doesn't have the correct code signature. The previous build was Xcode 13.2.1, and we can't build on Xcode 14 due to a dependency that needs to be updated.
Topic: App Store Distribution & Marketing SubTopic: TestFlight Tags:
Sep ’22
ERROR ITMS-90502: "Invalid Bundle. Apps that only contain the arm64 slice must also have 'arm64' in the list of UIRequiredDeviceCapabilities in Info.plist."
I get this error each time when I try to upload my iOS 11 only App to iTunes Connect:ERROR ITMS-90502: Invalid Bundle. Apps that only contain the arm64 slice must also have 'arm64' in the list of UIRequiredDeviceCapabilities in Info.plist.I have added<key>UIRequiredDeviceCapabilities</key> <array> <string>arm64</string> </array>to every Info.plist of my targets already!I also have set valid architectures in my build configuration to arm64 only.I am using Xcode 9 beta 5.Any idea how to fix that? Why does it not work even though I added UIRequiredDeviceCapabilities?
Topic: Code Signing SubTopic: Certificates, Identifiers & Profiles Tags:
49
0
23k
Sep ’22
Reply to [SKStoreProductViewController sceneDisconnected:] crash on iOS 15.7
I'm seeing this issue in one of the apps I work on. I saw it first in crashlogs (Bugsnag) in July but last 2 weeks the number of reported crashes skyrocketed. The app doesn't explicitly use the SKStoreProductViewController. It uses UIApplication.shared.open(itms-apps://apps.apple.com/app/appid) and the SKStoreReviewController.requestReview(), I'm not sure which one of these uses the SKStoreProductViewController. What is very odd, the other 2 apps that use the same way to show the other product app pages don't have this crash in their logs. Edit: I saw somebody mentioned the issue could be related to AdMob. This app also uses AdMob, the other 2 apps don't use AdMob.
Topic: App & System Services SubTopic: Core OS Tags:
Sep ’22