Search results for

ITMS-90158

1,681 results found

Post

Replies

Boosts

Views

Activity

OTA installation
I'm having an issue on ad-hoc OTA installation. I get my app archive via distribution (being automatically signed) with manifest.plist for OTA and upload it to dropbox account. However itms-service's action=download-manifest does not work for me with the dropbox URLs. I get the download link and add it to the manifest.plist. And then goes the link to download the manifest itself: itms-services://?action=download-manifest&url=https://www.dropbox.com/scl/fi/rzzlmbgx0duvd5gjb84uf/ManifestName.plist?rlkey=9j96n42qq8t1vwhcf3e7gxj8c&st=2hbhkidc&dl=1 I put the link on another web-site but it's not working. Nothing happens by pushing an install button with redirection link inside. And if I just copy the link and paste it in new page URL Safari asks me if I want to open it via iTunes and then still goes nothing. I'm not sure this is an issue either on apple and my app or dropbox with their links generation. Like a year ago it worked with the old link-generation. There was not rlkey parame
0
0
853
Jul ’24
Reply to Testing In-App Purchase promotion with App Store build before enabling on App Store
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:
Jul ’24
iTMS-90891: Missing required icon
I have an iPad app that we just added iPhone support to. It runs fine on the iPhone devices we've tested on. When we try to distribute the app by uploading it to App Store Connect the build doesn't show up in the TestFlight iOS Builds and we get an email from Apple Developer Relations that says this: Please correct the following issues and upload a new binary to App Store Connect. ITMS-90891: Missing required icon - The bundle does not contain an alternate app icon for iPhone / iPod Touch of exactly '120x120' pixels, in .png format for iOS versions >= 10.0. To support older versions of iOS, the icon may be required in the bundle outside of an asset catalog. Make sure the Info.plist file includes appropriate entries referencing the file. See https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleicons Apple Developer Relations We have followed the instructions on the web site and we have followed the instructions on other posts in this forum but nothing works. W
2
0
617
Jun ’24
Reply to Test flight app gets rejected, due to privacy file not find for FMDB.
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 .
Jun ’24
Release app to production with Xcode 16 beta and MacOS 15 beta
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...
4
0
3.0k
Jun ’24
Reply to TestFlight build upload with error ITMS-90338: Non-public API usage
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
Jun ’24
TestFlight build upload with error ITMS-90338: Non-public API usage
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
2
0
812
Jun ’24
App refused by Apple with error ITMS-90338: Non-public API usage
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
25
0
2.3k
Jun ’24
Reply to Transporter 1.3 Error
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
Jun ’24
Reply to ERROR ITMS-90823 Invalid entitlement. Bundle '*********' cannot use the 'com.apple.developer.on-demand-install-capable' entitlement. Remove the 'com.apple.developer.on-demand-install-capable' entitlement."
我的app在交付过程中保如下错误,搜代码 并未找到该方面的引用,想咨询下如何解决 ,谢谢 ERROR ITMS-90823: Invalid entitlement. Bundle 'HBuilder.app' cannot use the 'com.apple.developer.on-demand-install-capable' entitlement. Remove the 'com.apple.developer.on-demand-install-capable' entitlement.  ERROR ITMS-90918: Missing Info.plist value. The “HBuilder.app” bundle has the com.apple.developer.push-to-talk entitlement, but the required UIBackgroundModes Info.plist key value, push-to-talk, is not included.  ERROR ITMS-90926: Invalid entitlement. The “HBuilder.app” bundle has the com.apple.developer.media-device-discovery-extension entitlement, but only Media Device Discovery extensions should have this entitlement. Please remove the com.apple.developer.media-device-discovery-extension entitlement and upload a new build.
Topic: Programming Languages SubTopic: Swift Tags:
Jun ’24
xCode - ITMS-90111: Unsupported SDK or Xcode version
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...
2
0
1.1k
Jun ’24
Unsupported SDK or Xcode version (XCode 15.4 running on MacOS 15)
Hello! So I updated my mac to 15.0 Sequoia Developer Beta and couldn't run Xcode 15.4 because of the Mac version mismatch, so I installed Xcode 16 beta and archived my app, but of course I cannot publish it to App Store because Apple doesn't let you do it with beta soft. So, I downloaded Xcode 15.4 (current latest stable build) and managed to run it following this fix: https://stackoverflow.com/questions/69994916/how-can-i-run-older-xcode-version-on-new-macos-version But, now when I create a new archive and submit it for review I am getting: 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 tried deleting derived data and build folders, building new archives, but to no avail. Has anybody encountered this before?
12
0
18k
Jun ’24
ITMS-90809: Deprecated API Usage
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
5
0
977
Jun ’24
Impossible to define Proxy on Xcode 15
No Proxy for Xcode 15: _with Xcode 14 You can modify this file : /Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/Versions/A/itms/java/conf/net.properties and set the following property to true ( false by default ) java.net.useSystemProxies=true_ With Xcode 15, I don't found any solution **Utilisation of environment variables http_proxy and https_proxy it's useless because it's ignored #** how I can define a proxy in order to sign with Xcode command lines ?
1
0
561
Jun ’24