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?

Post not yet marked as solved Up vote post of busketeer Down vote post of busketeer
4.9k views
Posted by
busketeer
Reply

  • We had the same problem and want to know how to fix this. Thanks!

    —
    SunnyPro_

  • We didn't update AmazonIVSPlayer since our last submission and we're having the same issue, so there was definitely a change on Apple's side.

    —
    henrique

  • +1 = this is blocking our customers

    —
    s4sh

Accepted Reply

We believe we have resolved this issue and have updated the Apple Developer System Status page. If you continue to experience issues with your uploads, please contact Apple Developer Support.

Posted by
App Store Connect Engineer
Up vote reply of App Store Connect Engineer Down vote reply of App Store Connect Engineer
Post marked as solved

  • The issue is back again on 27 Jul 2023. Can you take a look at it again?

    —
    busketeer
Add a Comment

Replies

Same issue here. Waiting for a resolution.

Posted by
JuliaG
Up vote reply of JuliaG Down vote reply of JuliaG
Add a Comment

Any updates? Having the same trouble

Posted by
DinarKh
Up vote reply of DinarKh Down vote reply of DinarKh
Add a Comment

+1

Posted by
mgage86
Up vote reply of mgage86 Down vote reply of mgage86
Add a Comment

+1.. me and my customers still waiting for resolution. We use Bitmovin player SDK.

Posted by
Fernando_Leoncio25
Up vote reply of Fernando_Leoncio25 Down vote reply of Fernando_Leoncio25
Add a Comment

+1 We are having the same problem. We use Bitmovin Player SDK either

Posted by
WilliamTristao
Up vote reply of WilliamTristao Down vote reply of WilliamTristao
Add a Comment

+1

Posted by
leba
Up vote reply of leba Down vote reply of leba
Add a Comment

+1

Posted by
gabbas
Up vote reply of gabbas Down vote reply of gabbas
Add a Comment

Thanks for these reports, we are working on this issue and have updated the Apple Developer System Status page. We'll reply back when the issue is resolved.

Posted by
App Store Connect Engineer
Up vote reply of App Store Connect Engineer Down vote reply of App Store Connect Engineer
Add a Comment
  • 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.

Posted by
liu103
Up vote reply of liu103 Down vote reply of liu103
Add a Comment

We believe we have resolved this issue and have updated the Apple Developer System Status page. If you continue to experience issues with your uploads, please contact Apple Developer Support.

Posted by
App Store Connect Engineer
Up vote reply of App Store Connect Engineer Down vote reply of App Store Connect Engineer
Post marked as solved

  • The issue is back again on 27 Jul 2023. Can you take a look at it again?

    —
    busketeer
Add a Comment

I'm still having this issue as of a few minutes ago. Any one else as well?

Posted by
lwz7511
Up vote reply of lwz7511 Down vote reply of lwz7511
Add a Comment

Still facing this issue. +1

Posted by
vaibhavbansod
Up vote reply of vaibhavbansod Down vote reply of vaibhavbansod
Add a Comment

Now I'm able to upload the build to app store successfully with the framework. Thanks!

Posted by
busketeer
Up vote reply of busketeer Down vote reply of busketeer
Add a Comment

This issue is back

Posted by
martinkick
Post not yet marked as solved Up vote reply of martinkick Down vote reply of martinkick
Add a Comment

+1 This developed for me today. Yesterday no issue.

Posted by
chansencc
Post not yet marked as solved Up vote reply of chansencc Down vote reply of chansencc
Add a Comment