Hi,I used the following documentation: https://developer.apple.com/documentation/storekit/in-app_purchase/testing_promoted_in-app_purchases to test in-app purchase workflows initiated from the app store promotions. The test URL (itms-services://?action=purchaseIntent&bundleId=com.example.app&productIdentifier=product_name) worked just fine with a development build as it launched the app and initiated the purchase process but when I tried to use it with an app store build it didn't work (app would not launch). Is this the expected behavior? And if so, is there a way to test the workflow with app store builds before I enable the app store promotions?
Search results for
ITMS-90158
1,685 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
It seems to work for me, however I would like to show a certain screen when the app is opened through the itms-services://?action=purchaseIntent... URL. But when I tap the URL none of my App Delegate life cycle funcs are being called, except applicationWillResignActive, but can't read the information in the URL. Is there a way to read out the intent and productID when the app is being opened this way?
Topic:
App & System Services
SubTopic:
StoreKit
Tags:
ITMS-90338: Non-public API usage - The app references non-public selectors in myApp _isKeyDown, _modifiedInput, _modifierFlags, handleNotification:, isPassthrough, onSuccess:, removeValuesForKeys:completion:. 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.
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
Tags:
Enterprise
APNS
App Review
App Submission
Hi, we were able to migrate our solution from Xamarin to MAUI (.net 8). After a 2 weeks fight, the app is finally working on my dev devices. Unfortunately, after sending the app to review, it gets rejected because of the following: ITMS-90338: Non-public API usage - The app references non-public symbols in [Our app name]: _SCDynamicStoreCreate, _SCDynamicStoreCreateRunLoopSource, _SCDynamicStoreKeyCreateNetworkServiceEntity, _SCDynamicStoreSetNotificationKeys. 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/ From what I understand, this is because the 4 methods (_SCDynamicStoreCreate, _SCDynamicStoreCreateRunLoopSourc
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
I've updated my mac to Sequoia (MacOS 15) beta, my iPhone to iOS 18 beta, and Xcode to Xcode 16 beta. Only then, I realized I couldn't publish app updates with Xcode beta (error in AppStore Connect). I tried using the non-beta Xcode version but got Invalid Binary during app review: ITMS-90111: Unsupported SDK or Xcode version - App submissions must use the latest Xcode and SDK Release Candidates (RC). For details on currently supported versions, visit: https://developer.apple.com/news/releases. I really need to publish updates and I can't wait for September. I can't downgrade my devices because that would require me to erase both my Mac and my iPhone (for testing), which is not something I can do. Is there any option I didn't think about? How can I publish app updates in the current situation? It really should be more explicit before updating that you can't release updates with the beta versions...
App got rejected with this reason, ITMS-91065: Missing signature Your app includes “Frameworks/FMDB.framework/FMDB”, which includes FMDB, an SDK that was identified in the documentation as a privacy-impacting third-party SDK. If a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a signature file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a signature. For details about verifying the code signature for a third-party SDK, visit: https://developer.apple.com/documentation/xcode/verifying-the-origin-of-your-xcframeworks .
Topic:
Privacy & Security
SubTopic:
General
We've started hitting this limitation when submitting builds using Xcode Cloud. ITMS-90382: Upload limit reached - The upload limit for your application has been reached. Please wait 1 day and try again. We generate TestFlight builds for every PR (builds from PR get sent to QA & devs) & for every merge (builds get sent to everybody in the team). Is there any way to know what's the limit so we can try to work around it? Edit: I've just checked, and TestFlight only reports 19 builds that are expiring in 90 days (aka were uploaded within the last 24h). Is the limit that low?
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
App Store Connect
TestFlight
Xcode Cloud
Same issue here ITMS-90338: Non-public API usage - The app references non-public symbols in Contents/MacOS/ Flagged symbols: _AVCaptureDeviceSubjectAreaDidChangeNotification, _AVCaptureDeviceTypeBuiltInDualCamera, _AVCaptureDeviceTypeBuiltInDualWideCamera, _AVCaptureDeviceTypeBuiltInTelephotoCamera, _AVCaptureDeviceTypeBuiltInTripleCamera, _AVCaptureDeviceTypeBuiltInUltraWideCamera, _AVCaptureSessionPresetInputPriority
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
Hello, today when we uploaded a new TestFlight Mac Catalyst build we received an email about the build being invalid: TMS-90338: Non-public API usage - The app references non-public symbols in {app name}: _AVCaptureDeviceTypeBuiltInTelephotoCamera, _AVCaptureDeviceTypeBuiltInTrueDepthCamera, _AVCaptureDeviceTypeBuiltInUltraWideCamera, _AVCaptureSessionInterruptionReasonKey, _AVCaptureSessionInterruptionSystemPressureStateKey, _AVCaptureSystemPressureLevelCritical, _AVCaptureSystemPressureLevelFair, _AVCaptureSystemPressureLevelNominal, _AVCaptureSystemPressureLevelSerious, _AVCaptureSystemPressureLevelShutdown. 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://devel
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
AVAudioSession
AVFoundation
We are having the same issue on Catalyst with WebRTC. The following symbols are being flagged: ITMS-90338: Non-public API usage - The app references non-public symbols in Contents/Frameworks/WebRTC.framework/Versions/A/WebRTC: _AVCaptureSessionInterruptionReasonKey, _AVCaptureSessionPresetInputPriority
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
Our app submission is being rejected with the following error message: TMS-90809: Deprecated API Usage - New apps that use UIWebView are no longer accepted. Instead, use WKWebView for improved security and reliability. We have thoroughly scanned our code and all dependent libraries for references to UIWebView and found none. looking for help, on how to address this issue
Although I had accepted the answer from the App Store Connect Engineer (as it does get around the error in Transporter 1.3), it presented a new problem after uploading the app. Without the LSMinimumSystemVersion key in the Info.plist, I get an email from App Store Connect with the following issue: ITMS-90899: Macs with Apple silicon support issue - The app isn‘t compatible with the provided minimum macOS version of 11.5. It can run on macOS 12.0 or later. Please specify an LSMinimumSystemVersion value of 12.0 or later in a new build, or select a compatible version in App Store Connect. For details, visit: https://developer.apple.com/help/app-store-connect/manage-your-apps-availability/manage-availability-of-iphone-and-ipad-apps-on-macs-with-apple-silicon. The app minimum deployment is iOS 14.7. I tried setting the macOS minimum version for the app via the instructions (on App Store Connect - Pricing and Availability page) but I still get the issue email. This happens if I set it to Automatic (11.5) o
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
Hi,I updated to 10.15beta and started getting this error: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 9 and the SDK for iOS 11, tvOS 11, watchOS 4, or macOS 10.13 or later.My Xcode is still GM (10.2.1) so not sure what this error is trying to tell me, since I've been always keeping Xcode to stable version and MacOS on latest beta.Has anyone expriencing the same problem or have a solution to my issue ?Thanks.
When I try to upload an app to the AppStore, I receive following feedback: I had Xcode 16 with visionOS installed. Because of the feedback, I switched back to Xcode 15.3 with visionOs 1.0. I archived it again and tried to upload the app again. But I still receive the same feedback. I also tried https://stackoverflow.com/questions/56518791/app-store-refuses-my-update-after-installing-xcode-11-beta-with-keeping-xcode-10/56623421#56623421, but it seems that there is no such property for visionOS in the info.plist I do not have any further ideas...
Now receiving the following warning in Xcode when uploading app, and corresponding email. The app is unlikely to be released for Vision Pro. Is there any flag I've missed that can be added to the app to silence this (blacklist the device type), bearing in mind this app is not compiled with the Xcode Beta that supports Vision Pro. Failing that, can anyone suggest who to reach out to at Apple to request a solution? I realise this is only a warning, but it's an unwanted distraction. Dear Developer, We identified one or more issues with a recent delivery for your app, Cape Physio 0.52 (7). Your delivery was successful, but you may wish to correct the following issues in your next delivery: ITMS-90984: Apple Vision Pro support issue - The app contains the following UIRequiredDeviceCapabilities values, which aren’t supported on Apple Vision Pro. [accelerometer, gyroscope] After you’ve corrected the issues, you can upload a new binary to App Store Connect. Best regards, The App Store Team
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
App Store Connect
Xcode
App Submission
visionOS