'The app references non-public selectors in Payload'

Is this due to a bug on Apple's backend? I did not change the source code and trying to update my current app's version for Testflight. Please let me know how I can fix this.

Post not yet marked as solved Up vote post of taha-dev Down vote post of taha-dev
14k views
Posted by
taha-dev
Reply

  • Yeah, we have that as well. Actually not so easy to find out where it comes from. I ended up writing a python script that does an "objdump --syms --demangle" recursively over the entire build folder. Not sure yet whether this is something to worry about or as others pointed out just a bug in the verifier. Our build goes to testflight fine.

    —
    FlorianStoehr
Add a Comment

Replies

Looks like a bug, better file a feedback using the feedback app.

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

I am also encountering the same phenomenon.

This is caused by a selector in a third-party library that has the same name as an iOS private selector, but it does not occur in Xcode13, but in Xcode14.

I think it's probably a validation bug for iOS16.

As FB11488329 , I reported it to Feedback Assistant.

Posted by
mario25
Up vote reply of mario25 Down vote reply of mario25

  • Even with this warning message, I was able to upload the binary to App Store Connect.

    And it passed the review by Apple and was able to be distributed on the App Store. The delivered app is working fine.

    Since the message is "Distribution completed with warnings" instead of "Distribution failed with errors", it seems that the upload to App Store Connect was successful.

    —
    mario25

  • My build didn't show up in testFlight...

    —
    fireup

  • you have issue in :TwitterKit:placelD" please check this and after that you will able to upload

    —
    DhirenBharadava
Add a Comment

Is there a way to fix the issue?

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

Any update on this? I cannot push to TestFlight because of this

Posted by
KrsticM
Up vote reply of KrsticM Down vote reply of KrsticM

  • I am seeing the warning version of the above, in reference to some AWS SDK modules. I can still upload to App Store Connect and distribute via TestFlight.

    —
    LouK2
Add a Comment

I also believed it was preventing me from publishing to testflight but its not. Go look in AppConnect, the build is there.. Ignore and move on for now I guess.

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

Please check this one it might help you. [https://developer.apple.com/forums/thread/714224)

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

I still experience the same issue during an expo eas submission. This prevents a test-flight submission. Any hints how to start troubleshooting this?

Posted by
pushem
Post not yet marked as solved Up vote reply of pushem Down vote reply of pushem

  • how did you resolve this issue

    —
    nelnso
Add a Comment