Search results for

ITMS-90158

1,681 results found

Post

Replies

Boosts

Views

Activity

[RE-OPEN] ITMS-90338: Non-public API usage - The app references non-public symbols in Frameworks/AmazonIVSPlayer.framework/AmazonIVSPlayer: _CMTimebaseCreateWithMasterClock
Got this message from email when submitting an app to test flight around GMT+7 2pm. The app references non-public symbols in Frameworks/AmazonIVSPlayer.framework/AmazonIVSPlayer: _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/
3
0
621
Jul ’23
Reply to ITMS-90338: Non-public API usage-_CMTimebaseCreateWithMasterClock
It's back... https://github.com/aws-samples/amazon-ivs-player-ios-sample/issues/51#issuecomment-1652290123 App Store Connect Dear Developer, We identified one or more issues with a recent delivery for your app, My app 1.2.3 (4567). Please correct the following issues, then upload again. ITMS-90338: Non-public API usage - The app references non-public symbols in Frameworks/AmazonIVSPlayer.framework/AmazonIVSPlayer: _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
Jul ’23
ITMS-90078: Missing Push Notification Entitlement
Hi, Our project utilizes push notifications via OneSignal SDK. Everything looks correct and conforms with the documentation: The Push Notifications capability is enabled in XCode. The entitlements do contain the aps-environment key with the production value. I unpacked the resulting IPA and explored embedded.mobileprovision file - it does contain the aps-environment key with the production value in the Entitlements section too. The App ID and provision profiles used do include the Push Notification capability. So there's literally nothing to fix. Despite of that, when uploading the IPA to AppStore Connect, we receive an email with the warning ITMS-90078: Missing Push Notification Entitlement... that says there's no aps-environment entry. Moreover, the OneSignal dashboard indicates Missing Push Capabilities for all the iOS devices that run our application. Consequently, the push messages are not received. What could be wrong with the IPA and where to look at? Thanks in advance!
2
0
1.8k
Jul ’23
About "ITMS-90078: Missing Push Notification Entitlement" that comes when using Firebase Unity SDK
Questions When I installed the Firebase DynamicLinks Unity SDK and uploaded it to TestFlight, I have received an email from AppleStoreConnect stating ITMS-90078: Missing Push Notification Entitlement. Q1. is there any chance that leaving this situation unresolved will lead to rejection or suspension of distribution at the time of AppStore release? Q2. if anyone knows of a solution to this problem, please let me know. Background We are developing with Unity, a game development engine, outputting an Xcode project, and uploading it to TestFlight from Xcode. We have enabled Push Notification in the Capabilities setting of AppID, but we do not use this feature in our app, and we do not use a certificate for Push Notification. The same AppID setting did not send the same email until now, but when the Unity SDK for Firebase Dynamic Links was installed, the above email started to arrive. We believe that it is difficult to solve the problem at present, because there is a report on the Github issue of the SDK
0
0
1.3k
Jul ’23
Issue uploading release builds using ITMS Transporter: ITMS-90529 Invalid package
I'm dealing with a problem uploading our release binaries that is completely perplexing. If I use the ITMS Transporter desktop app to upload my IPA, everything works fine. If I use the ITMS Transporter command line interface (which i'm calling from inside the desktop app's directory /Applications/Transporter.app/Contents/itms/bin/iTMSTransporter -m upload...) to upload my IPA, I get the following error ERROR ITMS-90529: Invalid package. Applications built with sdk 9.0 or later must be packaged as proper IPA files. No idea why this error is coming up. I can also use altool to upload my binaries successfully. The issue is altool is being deprecated and I need to be able to use the ITMS command line interface as part of some deployment scripts we have. Please help!
5
0
1.3k
Jul ’23
TestFlight, Provisioning Profiles, and the Mac App Store
I regularly come across Mac developers who have an app in the Mac App Store but are unable to submit it to TestFlight. This post explains a common cause of that problem. If you have any questions or comments about this, start a new thread and tag it with Provisioning Profiles and TestFlight so that I see it. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com TestFlight, Provisioning Profiles, and the Mac App Store A provisioning profile authorises a device to run your app. For historical reasons, not all Mac apps need a provisioning profile. A Mac app only needs a profile if it uses a restricted entitlement, that is, an entitlement that must be authorised by a profile. For more background on this, see TN3125 Inside Code Signing: Provisioning Profiles and, specifically, its Entitlements on macOS section. IMPORTANT Your Mac App Store apps must be signed with the App Sandbox Entitlement, but that entitlement is unrestricted. This means that many M
0
0
5k
Jul ’23
Reply to ITMS-90338: Non-public API usage _CMTimebaseCreateWithMasterClock
1 I used API: CMTimebaseCreateWithSourceClock, not CMTimebaseCreateWithMasterClock, BUT when I remove the API : CMTimebaseCreateWithSourceClock, my app can normaly uploaded to appconnect without reject, after add CMTimebaseCreateWithSourceClock back, the message : ITMS-90338: Non-public API usage - The app references non-public symbols in : _CMTimebaseCreateWithMasterClock come back.
Jul ’23
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
552
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
ITMS-90338: Non-public API usage-_CMTimebaseCreateWithMasterClock
Yesterday it was still able to submit iOS App normally, but today it is not allowed because of this. I not import AVFCapture/AVFCore fmwk, and _CMTimebaseCreateWithMasterClock isn't non-public. ITMS-90338: Non-public API usage - The app references non-public symbols in Frameworks/libksygpulive.framework/libksygpulive: _CMTimebaseCreateWithMasterClock,The app links to non-public libraries in zhibo: /System/Library/PrivateFrameworks/AVFCapture.framework/AVFCapture, /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. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/ etc._CMTimebaseCreateWithMasterClock -… | Apple
20
0
3.3k
Jul ’23
ITMS-90338: Non-public API usage _CMTimebaseCreateWithMasterClock
Hi, our app build suddenly got rejected: ITMS-90338: Non-public API usage - The app references non-public symbols in Frameworks/AmazonIVSPlayer.framework/AmazonIVSPlayer: _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/ Our build's today at 0 AM GMT+0 is still passing the automatic review, but our build at 3 AM GMT+0 got this error. Our build both includes AmazonIVSPlayer.framework, but somehow got treated differently. Is there any change of rule from Apple side?
42
0
7.4k
Jul ’23