Search results for

ITMS-90158

1,681 results found

Post

Replies

Boosts

Views

Activity

ITMS-90338: Non-public API usage automatic refuse
Recently, I've got automatic response after archive my App into the testflight as above. Dear Developer, We identified one or more issues with a recent delivery for your app. Please correct the following issues, then upload again. ITMS-90338: Non-public API usage - The app references non-public selectors in Runner: initWithParentViewController:. 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 Problem is that I can't find the way to identify Non-public API usage on my code. I've build my app with Flutter, not swift. And there were no problem previous build, ver 2.0.15. Please let me kn
0
0
516
Jan ’23
Error Downloading FairPlay content using AVAggregateDownloadTask
During intermittent download attempts or deleting the existing download and retrying itm getting the following error: The operation couldn’t be completed. (CoreMediaErrorDomain error -12640.) Error Domain=CoreMediaErrorDomain Code=-12640 (null) UserInfo={_NSURLErrorRelatedURLSessionTaskErrorKey=(n BackgroundAVAssetDownloadTask <6476CB53-96B1-4AE6-88C3-EFDA3FC47F2F>.<2>n), _NSURLErrorFailingURLSessionTaskErrorKey=BackgroundAVAssetDownloadTask <6476CB53-96B1-4AE6-88C3-EFDA3FC47F2F>.<2>} The method which throws the error: func urlSession(_ session: URLSession, task: URLSessionTask, didCompleteWithError error: Error?) While downloading the content we prefetch the persistent key using AVContentKeySession and save that locally. Once we got the key successfully we start the download using AVAggregateDownloadTask. Hence we are not getting any issue in obtaining key or with the key exipry. Issue comes only at download attempt of that content. Background History of the issue: This issue
0
0
1.6k
Dec ’22
Need help uploading Swift App to App Store Connect
Hello, I am trying to upload a swift app to App Store Connect and I constantly get these following error messages. ITMS-90345: Metadata/Info.plist Mismatch - The value for bundle_short_version_string in the metadata.xml file does not match the value for CFBundleShortVersionString in Personal Task Tool [com.XXX.taskmanager.pkg/Payload/Personal Task Tool.app]. ITMS-90189: Redundant Binary Upload - You've already uploaded a build with build number '6' for version number '1.0.2'. Make sure you increment the build string before you upload your app to App Store Connect. Learn more in Xcode Help (http://help.apple.com/xcode/mac/current/#/devba7f53ad4). Can someone help me? P.S. For security purposes, I blocked out my real name with XXX.
0
0
850
Dec ’22
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
Dec ’22
Upload new build for a cancelled release (ITMS-90062)
I had a release for an app approved, but not yet released (3.3.0). Then I found a smal issue, so decided to cancel the release, because I wanted to use a new build for 3.3.0. 3.3.0 is now back in Prepare for Submission state. However, I can't upload my new build for the version: ERROR ITMS-90062: This bundle is invalid. The value for key CFBundleShortVersionString [3.3.0] in the Info.plist file must contain a higher version than that of the previously approved version [3.3.0]. Is there any way to get a new 3.3.0 build uploaded, or do I really have to create a 3.3.1 release instead?
0
0
589
Dec ’22
Reply to ITMS-90334 error when executing a Xcode Cloud TestFlight build
macOS 13.1 beta 4 addresses the issue creating ITMS-90334: Invalid Code Signature Identifier in Xcode Cloud. No update to Xcode is necessary to address the issue. This beta was released yesterday, and is available in Xcode Cloud when you configure a workflow to specify the macOS version used to execute your build. As this version is currently a beta, it is only available as part of the Latest Beta or Release macOS configuration, or as a dedicated choice for the macOS version, at this time. If you find this issue is not addressed with this configuration change to your Xcode Cloud workflow, continue to provide us feedback through Feedback Assistant, and share the FB numbers here so I can follow up on them.
Dec ’22
Missing recommended icon for iPad when using new xCode 14 single size app icon
Hi, We recently migrated our iOS app icon to use the new 'single size' feature in xCode 14. However upon submission to App Store Connect we are getting the following issues: ITMS-90892: Missing recommended icon - The bundle does not contain an alternate app icon for iPad of exactly '167x167' pixels, in .png format for iOS versions supporting iPad Pro. To support older operating systems, 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 ITMS-90892: Missing recommended icon - The bundle does not contain an alternate app icon for iPad of exactly '152x152' pixels, in .png format for iOS versions >= 10.0. To support older operating systems, 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
2
0
1k
Dec ’22
Noticing Strange things trying to fix my non-public API uses, blank project uploads ok, then all others fail
I get the error when uploading to test flight ITMS-90338: Non-public API usage - The app contains one or more corrupted binaries. Rebuild the app and resubmit. I decided to use a blank unreal engine project and it works uploading to test flight, I am trying to find which 3rd party plugin is causing it. So everytime I add or remove a plugin, I generate new xocde file so it can pick up the changes. so I think I pin point it to a 3rd party plugin. The only thing is, when I try on a blank project it works, if I start adding plugins, it stops working, but if I go back to the original set up I keep getting the error when trying to upload again. are there steps I am missing? Are we suppose to clean the project in xcode first, maybe remove some files in derived data folder or archives? and then rebuild? are there any sudo terminal commands that can help? I am trying again right now , I am using the same project and removed all the folders xcode generates and then built the game again with the blank project t
0
0
452
Nov ’22
Cant upload to TestFlight, ITMS-90338: Non-public API usage
I keep getting emails saying my app cant be processed, how can I fix it or find out whats causing it. Dear Developer, We identified one or more issues with a recent delivery for your app, EmbryosIOS 0.1 (0.99). 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 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
3
0
813
Nov ’22
ITMS-90338: Non-public API usage automatic refuse
HI! We received this message from technical support Multiline ITMS-90338: Non-public API usage - The app references non-public selectors in SMMplanner: _isKeyDown, _modifiedInput, _modifierFlags. 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/ BlockQuote but problem is that _isKeyDown, _modifiedInput, _modifierFlags are is internal react-native library methods! And we can't do nothing to fix it. So how can we solve this problem?
0
0
461
Nov ’22
ERROR ITMS-90164: Invalid Code Signing Entitlements
Hi team,When uploading the ipa via transporter command line utility, the following message is returned. We are re-signing manually and curiously, the errors only occurs for app extensions and not the main app. ERROR ITMS-90164: Invalid Code Signing Entitlements. The entitlements in your app bundle signature do not match the ones that are contained in the provisioning profile. According to the provisioning profile, the bundle contains a key value that is not allowed: '''TeamId.ExtBundleId''' for the key '''application-identifier''' in '''Payload/MyApp.app/PlugIns/MyAppExtension/MyAppExtension'''. We are signing manually and our app entitlements are as such <plist version=1.0> <dict> <key>application-identifier</key> <string>TeamId.ExtBundleId</string> <key>aps-environment</key> <string>production</string> <key>beta-reports-active</key> <true/> <key>com.apple.developer.team-identifier</key> <string>TeamId<
0
0
936
Nov ’22