Search results for

ITMS-90158

1,686 results found

Post

Replies

Boosts

Views

Activity

Non-public API usage - The app references non-public symbols in app: _CMTimebaseCreateWithMasterClock.
App Store Connect 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 symbols in app: _CMTimebaseCreateWithMasterClock. 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 But the API used by the project is CMTimebaseCreateWithSourceClock.
1
0
554
Jul ’23
Reply to ITMS-90338: Non-public API usage _CMTimebaseCreateWithMasterClock
Hi, same is being reported by multiple customers of our player iOS SDK when submitting their applications today. We have confirmed that _CMTimebaseCreateWithMasterClock is not called from SDK code. The only related API usage is CMTimebaseCreateWithSourceClock which is not private API and this is not new code. The app submission error is encountered only today and the submissions worked earlier with same BitmovinPlayer code. Could this be an Apple issue same as the previously acknowledged bug for MacOS in this thread? ITMS-90338: Non-public API usage - The app references non-public symbols in Frameworks/BitmovinPlayer.framework/BitmovinPlayer: _CMTimebaseCreateWithMasterClock. 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 f
Jul ’23
Reply to ITMS-90338: Non-public API usage _CMTimebaseCreateWithMasterClock
Hi, we are facing the same issue, with the same email response: ITMS-90338: Non-public API usage - The app references non-public symbols in Frameworks/AmazonIVSPlayer.framework/AmazonIVSPlayer: _CMTimebaseCreateWithMasterClock. ... Builds from yesterday passed submission, but not today. AmazonIVSPlayer.framework is the same in both cases. many reports here
Jul ’23
Reply to _CMTimebaseCreateWithMasterClock - ITMS-90338: Non-public API usage
Hi Developers, same is being reported by multiple customers of our player iOS SDK when submitting their applications today. We have confirmed that _CMTimebaseCreateWithMasterClock is not called from SDK code. The only related API usage is CMTimebaseCreateWithSourceClock which is not private API and this is not new code. The app submission error is encountered only today and the submissions worked earlier with same BitmovinPlayer code. Could this be an Apple issue same as the previously acknowledged bug for MacOS in this thread? ITMS-90338: Non-public API usage - The app references non-public symbols in Frameworks/BitmovinPlayer.framework/BitmovinPlayer: _CMTimebaseCreateWithMasterClock. 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 rem
Jul ’23
2021-6 Missing Info.plist value - A value for the Info.plist key 'CFBundleIconName' is missing in the bundle, even then I include CFBundleIconName.
I develop an APP with Xamarin, Visual Studio. I publish my app to App Store I got message from Apple. Dear Developer, We identified one or more issues with a recent delivery for your app, XXX APP 1.5.6 (1.5.14). Please correct the following issues, then upload again. ITMS-90713: Missing Info.plist value - A value for the Info.plist key 'CFBundleIconName' is missing in the bundle 'com.XXXX.XXXX'. Apps built with iOS 11 or later SDK must supply app icons in an asset catalog and must also provide a value for this Info.plist key. For more information see http://help.apple.com/xcode/mac/current/#/dev10510b1f7. Best regards, The App Store Team My info.plist file include CFBundleIconName. I include CFBundleIconName in my info.plist file. UIDeviceFamily 1 2 UISupportedInterfaceOrientations UIInterfaceOrientationPortrait UISupportedInterfaceOrientations~ipad UIInterfaceOrientationPortrait UIInterfaceOrientationPortraitUpsideDown UIInterfaceOrientationLandscapeLeft UIInterfaceOrientationLandscapeRight
9
0
7.9k
Jul ’23
ITMS-90338: Non-public API usage
Hello, We contacted Apple Developer Support due to an automatic message we receive when trying to publish a new version of our app The app links to non-public libraries in Frameworks/UnityFramework.framework/UnityFramework: /System/Library/PrivateFrameworks/AVFCore.framework/AVFCore. 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. The problem is we do not understand what the issue is even when reading your automatic message. How can we debug this ? How can we identify the source of the problem ? Do you have any idea of what the problem is ? What we tried : We tried to re-publish the application we currently have on your store (production) with different build number => App rejected with the same automatic message ; We tried to look fo
2
0
589
Jul ’23
ITMS-90427: Invalid Swift Support
Hi, I'm using React-Native and XCode 12.5.1. Since the last update of XCode, I receive this error by mail when I upload my archive : We identified one or more issues with a recent delivery for your app, *** 1.28.5 (83). Please correct the following issues, then upload again. ITMS-90427: Invalid Swift Support - The expected dylibs are missing from the app’s Framework location, such as /Payload/***.app/Frameworks. I don't touch anything, but I can't put a new buld on the App Store...
2
0
1.9k
Jun ’23
Info.Plist localized issue
when I submit my product recently, I meet the below issue from Apple, but such product before already submit successfully and my xxx-Info.plist and InfoPlist.strings are matched, but why happen The “NSContactsUsageDescription” value for the NSContactsUsageDescription key isn’t allowed in “xxx.app”? any rule changed recently? thanks for your help! App Store Connect Dear Developer, We identified one or more issues with a recent delivery for your app, 1.0.25 (84). Your delivery was successful, but you may wish to correct the following issues in your next delivery: ITMS-90738: Invalid purpose string value - The “NSContactsUsageDescription” value for the NSContactsUsageDescription key isn’t allowed in “xxx.app”. 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 “xxx.app” bundle should contain a NSContactsUsageDescription key with a user-facing purpose string explaining clearly and comple
1
0
2.6k
Jun ’23
Uploading iOS 10 beta app gives an error - ITMS-90334
I am trying to upload an app using Xcode 8 beta 6. It is compiled against iOS 10 beta SDK. It has extensions which are also compiled for that SDK. The watchOS app is compiled against watchOS 3 SDK. When I upload it to Testflight through Xcode and Application Loader, it returns back with an errorERROR ITMS-90334: Invalid Code Signature Identifier. The identifier com.apple.WK in your code signature for WatchOSApp must match its Bundle IdentifierCan some one help me solve this issue ?Thanks!
5
0
2.2k
Jun ’23
Xcode 15.0 beta 15A5160n upload IPA fail
I receive this mail after deliver my app for a while: ITMS-90338: Non-public API usage - The app links to non-public libraries in Runner: /System/Library/PrivateFrameworks/AVFCapture.framework/AVFCapture, /System/Library/PrivateFrameworks/AVFCore.framework/AVFCore...... I didn't use these API in my code. By the way I could upload my app successfully with Xcode 14 without this error.
2
0
876
Jun ’23
Invalid Bundle Error When Uploading App to App Store
Hi all, I recently uploaded my app to the App Store and received the following error message: ITMS-90961: Invalid bundle - The app at 'xxx.app' contains a single-size app icon but has a value of 11.0 for the MinimumOSVersion key in its Info.plist file. Include all app icon sizes to support iOS 11.0 or later, or update the iOS Deployment Target to 12.0 or later to support uploads with a single-size app icon. I have checked my assets and confirmed that the AppIcon is set to All Sizes and not Single Size. Is this an issue with Apple's systems or is there something I am doing wrong? Any help would be greatly appreciated. My Xcode version is 14.3 Thanks in advance.
6
0
3.8k
Jun ’23
Arcade Options Entitlements for TestFlight Deployment
We're attempting to build and distribute our MacOS game via TestFlight and are met with an error or multiple errors regarding com.apple.developer.arcade-operations. Either we exclude the entry from our entitlements file used to sign and get this single error: ITMS-90769: Invalid Bundle - Apple Arcade apps require the 'com.apple.developer.arcade-operations' entitlement. Or we add it to the entitlements and get this error: ITMS-90287: Invalid Code Signing Entitlements - The entitlements in your app bundle signature do not match the ones that are contained in the provisioning profile. The bundle contains a key that is not included in the provisioning profile: 'com.apple.developer.arcade-operations' in 'com.[CompanyIdentifier.GameName].pkg/Payload/[GameName].app/Contents/MacOS/[GameName]'. We're unsure of how to properly include the key'' in the provisioning profile. There are no options to do such a thing on the developer.apple website where they're created/editable and I can't just add it to t
3
0
3.2k
Jun ’23
Reply to Crypting ITMS-90886 error abound bundles identifiers and provisioning profiles
I've received the same error as well. I'm using electron with nested helper applications (e.g. Main.app/Contents/Frameworks/Helper.app) The following causes the error for me codesign -s $DISTRIBUTION_KEY -f --entitlements $CHILD_PLIST packages/mas-universal/{APP_NAME}.app/Contents/Frameworks/{APP_NAME} Helper (Renderer).app productbuild --component packages/mas-universal/{APP_NAME}.app /Applications --sign $INSTALLER_KEY packages/{APP_NAME}.pkg -- This seems to fix the error, but causes a new error codesign --sign {40-char-hash-from-electron/osx-sign} --force --timestamp --options runtime --entitlements $CHILD_PLIST packages/mas-universal/{APP_NAME}.app/Contents/Frameworks/{APP_NAME} Helper (Renderer).app productbuild --component packages/mas-universal/{APP_NAME}.app /Applications --sign $INSTALLER_KEY packages/{APP_NAME}.pkg -- WARNING ITMS-90885: Cannot be used with TestFlight because the executable “${executable}” in bundle “${bundle}” is missing a provisioning profile but has an application ident
Topic: Code Signing SubTopic: General Tags:
May ’23
ITMS-90338: Non-public API usage
Hello, we are having this response when submitting our application, but in the return email from the Apple Store Connect it does not show what would be the point to correct. Is anyone else having this too? any idea what to do? Thanks in advance.. 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 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
1
0
913
May ’23