Search results for

ITMS-90158

1,681 results found

Post

Replies

Boosts

Views

Activity

Nested code is modified or invalid issue when submitting a macOS app to App Store
Hello, Im currently having signing issues submitting my Swift macOS app to App Store Connect. After submitting it using Xcode I receive an e-mail with these issues: ITMS-90238: Invalid Signature - The main app bundle CodeMenu at path CodeMenu.app has following signing error(s): nested code is modified or invalid . Refer to the Code Signing and Application Sandboxing Guide at http://developer.apple.com/library/mac/#documentation/Security/Conceptual/CodeSigningGuide/AboutCS/AboutCS.html and Technical Note 2206 at https://developer.apple.com/library/mac/technotes/tn2206/_index.html for more information. ITMS-90238: Invalid Signature - The nested app bundle CodeMirror-SwiftUI at path CodeMenu.app/Contents/Frameworks/CodeMirror-SwiftUI.framework has following signing error(s): valid on disk /Volumes/workspace/app_data/SWValidationService/mz_15562079435119469448dir/mz_7860448159412669971dir/id.thedev.marcin.CodeMenu.pkg/Payload/CodeMenu.app/Contents/Frameworks/CodeMirror-SwiftUI.framework/Versions
1
0
807
Feb ’24
ITMS-90683: Missing purpose string in Info.plist - NSLocationAlwaysAndWhenInUseUsageDescription
In our latest two pushes to AppStore Connect, we've been getting the following message, where we hadn't previously: Dear Developer, We identified one or more issues with a recent delivery for your app, XYZ 1.2.3 (123). Your delivery was successful, but you may wish to correct the following issues in your next delivery: ITMS-90683: Missing purpose string in Info.plist - Your app’s code references one or more APIs that access sensitive user data, or the app has one or more entitlements that permit such access. The Info.plist file for the “xyz.app” bundle should contain a NSLocationAlwaysAndWhenInUseUsageDescription 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. Oddly though, we've not really made any changes to our codebase that should trigger this. Just wondering if others ar
10
0
16k
Jun ’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
Uploading failed with ERROR ITMS-90045: Invalid Code Signing Entitlements
When I try to submit the app, I get the following error. Is there a way to solve this? Asset validation failed (90045) Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, key 'UIRequiresFullScreen' in 'Payload/MyApp.iOS.app/MyApp.iOS' is not supported. Asset validation failed (90045) Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, key 'CFBundleDisplayName' in 'Payload/MyApp.iOS.app/MyApp.iOS' is not supported. Asset validation failed (90045) Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, key 'UIMainStoryboardFile' in 'Payload/MyApp.iOS.app/MyApp.iOS' is not supported. Asset validation failed (90045) Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that
4
0
868
Jan ’24
Uploading failed with ERROR ITMS-90045: Invalid Code Signing Entitlements
When I try to submit the app, I get the following error. Is there a way to solve this? Asset validation failed (90045) Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, key 'UIRequiresFullScreen' in 'Payload/MyApp.iOS.app/MyApp.iOS' is not supported. Asset validation failed (90045) Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, key 'CFBundleDisplayName' in 'Payload/MyApp.iOS.app/MyApp.iOS' is not supported. Asset validation failed (90045) Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, key 'UIMainStoryboardFile' in 'Payload/MyApp.iOS.app/MyApp.iOS' is not supported. Asset validation failed (90045) Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that
1
0
547
Jan ’24
Marketing/App Store Icon PNG transparency issue
I'm trying to submit my app and ran into this error:Missing Marketing Icon - iOS Apps must include a 1024x1024px Marketing Icon in PNG format. Apps that do not include the Marketing Icon cannot be submitted for App Review or Beta App Review.So, I updated my asset catalog to include one, but now I keep getting this error:ERROR ITMS-90717: Invalid App Store Icon. The App Store Icon in the asset catalog in 'Some.app' can't be transparent nor contain an alpha channel.I have removed alpha and transparency with multiple Apps (Photoshop, pngcrush, imagemagick) but keep running into the validation error above. I'm pretty sure my PNG file does not contain any alpha channels or transparency at this point. The only way I found to pass validation is to supply the marketing icon in JPG format, contrary to the first error message.Anybody with similar issues or ideas how to pass validation with a PNG App Store icon?
44
0
50k
Mar ’22
Reply to Issue uploading release builds using ITMS Transporter: ITMS-90529 Invalid package
i'm starstruck haha This is with the exact same IPA file. I know you're asking the guy who was trying on Linux, but I want to also highlight that the same IPA file uploaded via the GUI of the MacOS Transporter app works, while passing that IPA into the command line interface for Transporter doesn't work. I suspect the MacOS Transporter GUI is using a slightly different version of the ITMS Transporter binary than the CLI or Linux Transporter app are.
Jan ’24
WARNING ITMS-90704: Missing App Store Icon.
Hi,I have been trying to resolve another warning.WARNING ITMS-90704: Missing App Store Icon. iOS Apps must include a 1024x1024px App Store Icon in PNG format. Without providing the icon in the Asset Catalog or via iTunes Connect, apps cannot be submitted for App Review or Beta App Review. Refer to https://developer.apple.com/ios/human-interface-guidelines/icons-and-images/app-icon/ for more information.Any help would be greatful.iOS11 / Xcode 9.0.1 / Mac High Sierra 10.13
16
0
23k
Jul ’21
ITMS-90429: Invalid Swift Support 
Hi, I am facing a problem with Xcode 12.3, swift 5, and cocoapods-1.10.1 version when I want to publish my archive on Appstore Connect, everything goes well, but once the application sent I receive an e-mail from App Store Connect with the following error : ITMS-90429: Invalid Swift Support - The files libswiftDarwin.dylib, libswiftMetal.dylib, libswiftCoreAudio.dylib, libswiftsimd.dylib, libswiftQuartzCore.dylib, libswiftos.dylib, libswiftObjectiveC.dylib, libswiftDispatch.dylib, libswiftCoreLocation.dylib, libswiftAccelerate.dylib, libswiftCoreGraphics.dylib, libswiftCoreData.dylib, libswiftCoreFoundation.dylib, libswiftUIKit.dylib, libswiftCoreMedia.dylib, libswiftAVFoundation.dylib, libswiftContacts.dylib, libswiftCore.dylib, libswiftFoundation.dylib, libswiftMediaPlayer.dylib, libswiftCloudKit.dylib, libswiftCoreImage.dylib aren’t at the expected location /Payload/WoWonder.app/Frameworks. Move the file to the expected location, rebuild your app using the current public (GM) version of Xcode, and
3
0
3.7k
Aug ’22
IOS app works on testfligth but rejected on review accusing of Beta version of XCode. But my XCode is 14.1
I have seen several posts around the internet from years past with complains of such a problem, the review is rejected with : ITMS-90111: Invalid Toolchain - Your app was built with a beta version of Xcode or SDK. Apps submitted to the App Store must be built with the GM version of Xcode 10.1 and the SDK for iOS 12.1 and watchOS 5.1, Xcode 7.1 and the SDK for tvOS 9, or Xcode 6 and the SDK for macOS 10.9 or later. If you are using an Xcode beta version to test your app, make sure you are using the latest supported version. My XCode is 14.1 and I am using github Continuous integration to build it. Any hint on how can I track what is wrong? Each and every post I found on the subject ended either without any answer or just saying to wait for apple to fix it.
1
0
426
Jan ’24
Not working Testing Promoted In-App Purchases in iOS16
I use the promotion function (https://developer.apple.com/documentation/storekit/in-app_purchase/original_api_for_in-app_purchase/promoting_in-app_purchases)) within the app. It worked well up to the iOS15 environment, but during the iOS16 beta test, it was confirmed that it did not work properly. When tested according to the guide (https://developer.apple.com/documentation/storekit/in-app_purchase/original_api_for_in-app_purchase/testing_promoted_in-app_purchases)), iOS15 calls paymentQueue:shouldAddStorePayment:delegate normally, but iOS16 does not call paymentQueue:shouldAddStorePayment:. The link used for the test is itms-services://?action=purchaseIntent&bundleId=com.nhn.cloud.client.sdk&productIdentifier=com.nn.cloud.iap.gem99 Is there a problem with iOS16?
1
0
801
Aug ’22
App binary rejected - potential XCode back end bug?
Hi, our app - that has been successfully being updated every few weeks on Testflight for years now - suddently (although still compiling and running fine on a device connected to Xcode) fails validation & upload to Testflight. The error message does not give any info, other than Asset validation failed - The app contains one or more corrupted binaries. Rebuild the app and resubmit (ID: 718a52a4-fed6-49ac-a025-8d62f6285cd2). The follow up email, says : We identified one or more issues with a recent delivery for your app, Name of app 1.23 (1.23). 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 you
2
0
1.4k
Dec ’23
ITMS-90424: Invalid Swift Support
Hello I have a problem with Xcode when I want to publish my archive on Appstore Connect, everything goes well, but once the application sent I receive an e-mail from App Store Connect with the following error :Dear Developer,We identified one or more issues with a recent delivery for your app, Notorioustrade 1.4 (1). Please correct the following issues, then upload again.ITMS-90424: Invalid Swift Support - The SwiftSupport folder is empty. Rebuild your app using the current public (GM) version of Xcode and resubmit it.Best regards,The App Store TeamConfiguration :Mac Os Mojave 10.14.16Xcode Version 11.2.1 (11B500)My application is a simple WKWebView with cocoapods for OneSignal Notification extension.I really need Help, i have try to call Apple but the services don't know where the problem come from.
16
0
29k
Jan ’23