ITMS-90158

Hello, I have a question regarding the Privacy Manifest of a third-party SDK. We are using a static third-party SDK. This third-party SDK use the UserDefaults API, and it is also specified in the Privacy Accessed API Types within PrivacyInfo.xcprivacy. The static third-party SDK is added as a dependency via CocoaPods, and PrivacyInfo.xcprivacy is included in the Pods Resource. Additionally, our app does not use UserDefaults API. When we generate the Privacy Report, it correctly shows the data collected by the third-party SDK. However, when we submitted for review, we received a warning email stating that UserDefaults is being used in the app but is missing from the Privacy Manifest. ITMS-91053: Missing API declaration - Your app’s code in the “MyApp” file references one or more APIs that require reasons, including the following API categories: NSPrivacyAccessedAPICategoryUserDefaults. While no action is required at this time, starting May 1, 2024, when you upload a new app or app update, you must inc

Am tired of asking my boss to forward me the emails they get from Apple with the subject The uploaded build for XXXX has one or more issues. I am trying to debug issues such as ITMS-91053: Missing API declaration as we deal with our 3rd party package usage. What permissions, privileges do I need to get those emails?

We are getting warnings from Apple, ITMS-91053 Missing API declaration, for categories Disk Space, Timestamp, and more. But we've checked our source code to make sure we are not making any of the entry points at issue. We suspect they are being called from one of the 3rd party frameworks we use, some of them are binary xcframeworks. Is Apple planning on extending their warnings to provide more information about where the usages are? Are we left to find it ourselves? Do we need to resort to adding those reasons to our app's manifest? Which seems hacking since we probably don't know when of the allowed reasons are accurate.

When an update is available for my unlisted private app, I would like to notify my users. That part is easy. As part of this notification, I would like to give my users the option to click a button sending them directly to a page in the App Store, where they can update the app. I cannot figure out how to do this. I have tried with the following links: https://apps.apple.com/app/id https://apps.apple.com/us/app/vh-ordrer/id itms-apps://itunes.apple.com/app/id But all of the links give me the same message: App not available: This app is currently not available in your country or region. The app is made available through MDM. Is there a way to generate a direct link to the App Store page for my Private app? If not, then I would like to know if there is a way to link users directly to the Account pop over in the App Store?

I am having trouble submitting the next build of my macOS app to the App Store Connect. I keep getting a variation of this error: ITMS-90238: Invalid Signature - The main app bundle MyApp at path MyApp.app has following signing error(s): code has no resources but signature indicates they must be present In subcomponent: MyApp.app/Contents/Frameworks/GoogleAppMeasurement.framework . 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 main app bundle MyApp at path MyApp.app has following signing error(s): code has no resources but signature indicates they must be present In subcomponent: MyApp.app/Contents/Frameworks/GoogleAppMeasurementIdentitySupport.framework . Refer to the Code Signing and Application Sandboxing Guide

This is the mail I received from Apple while testing. If you look at it, it shows that there are two items that are problematic. As you can see, ITMS-91053: Missing API decimation shows the same problem in both, but the colors are displayed differently. (Purple, Gray) There were four problems in the mail I received while testing more, but all of them received the same color. Is this just a mail error?? Or does the color have a meaning?

Hi, Please help! I have trouble uploading my app to App Store. I'm using Transporter to upload my ipa package, and I always get following error in my email: ITMS-90428: Invalid Swift Support - The files libswift_Concurrency.dylib don’t match /Payload/CreatiApp.app/Frameworks/libswift_Concurrency.dylib. Make sure the files are correct, rebuild your app, and resubmit it. Don’t apply post-processing to /Payload/CreatiApp.app/Frameworks/libswift_Concurrency.dylib. What should I do. I tried copy and paste old libswift_Concurrency.dylib, but it doesn't work at all

Hi guys, need some help on this issue when I submit my testing app to TestFlight using GitHub Actions and Fastlane, I get this warning from App Store Connect: We noticed one or more issues with a recent delivery for the following app: Although delivery was successful, you may want to correct the following issues in your next delivery. Once you've corrected the issues, upload a new binary to App Store Connect. ITMS-90725: SDK version issue - This app was built with the iOS 16.2 SDK. Starting April 29, 2024, all iOS and iPadOS apps must be built with the iOS 17 SDK or later, included in Xcode 15 or later, in order to be uploaded to App Store Connect or submitted for distribution. I am using React Native CLI, and Fastlane to run and build my app through Github Actions. After scouring around, from what I understood was that all I needed to do was just to update my Xcode and iOS SDK to the latest, which I did. Currently my Xcode is 15.2 and iOS SDK is on 17 already. However, I still receive this warning w

So I have an app live in the app store all good, however I am now developing an update to it that adds the ability to allow photos to be used and that requires that the app gets an additional access to the camera roll. Now on upload to testflight I get this error emailed to me, not in the interface: ITMS-90109: This bundle is invalid - The key UIRequiredDeviceCapabilities in the Info.plist may not contain values that would prevent this application from running on devices that were supported by previous versions. To me that is saying that I cant add new features to an app that requires additional permissions. Is that correct? How can I get around this, will my app get rejected when I submit it due to this, or is it just an information item?

I'm trying to upload a version with Compose multiplatform dependencies, and I get an email: Please correct the following issues and upload a new binary to App Store Connect. ITMS-90338: Non-public API usage - The app references non-public symbols in Nanit: _ubidi_close, _ubidi_getDirection, _ubidi_getLength, _ubidi_getLevelAt, _ubidi_openSized, _ubidi_reorderVisual, _ubidi_setPara, _ubrk_clone, _ubrk_current, _ubrk_first, _ubrk_getRuleStatus, _ubrk_getRuleStatusVec, _ubrk_isBoundary, _ubrk_last, _ubrk_next, _ubrk_previous, _uloc_getDefault, _uloc_toLanguageTag, _uscript_getScript. 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. When I run the validation from Xcode it works. Can you please advice?

Hello, We noticed one or more issues with a recent delivery for the following app: xyz Version 3.0.0 Build 18396 Please correct the following issues and upload a new binary to App Store Connect. ITMS-90338: Non-public API usage - The app references non-public symbols in Frameworks/xyz.framework/xyz: _dyld_shared_cache_file_path. 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/