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 Developer Forums

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

  • I'm also facing exactly the same issue. Hope team Apple will resolve it soon.

    —
    mo.ag
Add a Comment

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

  • @App Store Connect Engineer Thank God, nice job.

    —
    AnakinChen

  • Hi, we got the same email from App Store Connect again today.

    Can you check this and solve it ASAP? We have a scheduled build to release...

    —
    OliverSB

  • @App Store Connect Engineer Hi, We tried to re-upload today Jul, 27 12:00 pm (UTC). The error persisted on our end.

    The error thrown:** ITMS-90338: Non-public API usage-_CMTimebaseCreateWithMasterClock**

    —
    Heatclift24

Replies

Hello, thanks for posting about this error. We are investigating this issue. If there are any others experiencing this issue, please file a support request at Apple Developer Support.

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

  • These people all have the same problem. Thank you for investigating, Hope to have results for submission as soon as possible. Thank you.

    —
    Gua

  • Are there any updates on this? We're approaching our release date and this really impacts our development. Thanks.

    —
    JuliaG
Add a Comment

@App Store Connect Engineer

https://developer.apple.com/forums/thread/733318 https://github.com/aws-samples/amazon-ivs-player-ios-sample/issues/51 https://github.com/ksvc/KSYLive_iOS/issues/201

These people all have the same problem. Thank you for investigating, Hope to have results for submission as soon as possible. Thank you.

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

Hi we experienced the exact same issue since Jul 6. Any solution to this issue yet?

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

Any Update ? TF ipa can't uploaded.....

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

Hi I'm facing same issue any help?

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

Any update?

Posted by
mmmcl
Up vote reply of mmmcl Down vote reply of mmmcl
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
Post not yet marked as solved Up vote reply of App Store Connect Engineer Down vote reply of App Store Connect Engineer
Add a Comment

Same problem here.

https://github.com/aws-samples/amazon-ivs-player-ios-sample/issues/51

Posted by
henrique
Up vote reply of henrique Down vote reply of henrique
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

  • @App Store Connect Engineer Thank God, nice job.

    —
    AnakinChen

  • Hi, we got the same email from App Store Connect again today.

    Can you check this and solve it ASAP? We have a scheduled build to release...

    —
    OliverSB

  • @App Store Connect Engineer Hi, We tried to re-upload today Jul, 27 12:00 pm (UTC). The error persisted on our end.

    The error thrown:** ITMS-90338: Non-public API usage-_CMTimebaseCreateWithMasterClock**

    —
    Heatclift24

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

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

+1.

We are also seeing this again as of July 26, 2023.

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

It's back again.

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

We're experiencing it again too

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

It's back again.

Posted by
ios-
Up vote reply of ios- Down vote reply of ios-
Add a Comment

same problem here too

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