Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. We have updated the language to the Editor Terms based on feedback from our employees and community. Learn more.
    Dismiss Notice

Bug Warning when uploading Xcode14 builds to AppStoreConnect, Unity uses private API [2021.3.8f1]

Discussion in 'iOS and tvOS' started by Bersaelor, Sep 14, 2022.

  1. Bersaelor

    Bersaelor

    Joined:
    Oct 8, 2016
    Posts:
    110
    After updating to Xcode 14, I get the following warning:

    This could cause problems when we want to send our app to apple review as they usually don't allow private APIs to be called.
    We don't use any Push-Notifications in our code, the method mentioned seems auto generated by Unity.

    appstoreconnect warning.png
     
  2. Yandalf

    Yandalf

    Joined:
    Feb 11, 2014
    Posts:
    491
    Same issue here! Worked fine a day ago then after XCode update everything goes down the crapper.
    Reverting to 13.4 for now, but this better get looked at.
     
  3. smithmw9

    smithmw9

    Joined:
    Feb 9, 2018
    Posts:
    4
    Same issue, can't distribute anything to Apple Connect
    The app references non-public selectors in Payload/a.app/Frameworks/UnityFramework.framework/UnityFramework: applicationWillFinishLaunchingWithOptions:, didReceiveRemoteNotification:, loadPlugin
     
    tvalleau and ameralay like this.
  4. Neonlyte

    Neonlyte

    Joined:
    Oct 17, 2013
    Posts:
    505
    This is likely to be a false positive of Xcode 14. Those selectors come from AppDelegateListener from Classes/PluginBase/AppDelegateListener.h/mm. Those are part of the interface declarations for native plugins, which is not actual private API usage, and Xcode should not have flagged it, given Xcode 13 is fine with it. It could be just a simple clash with an actual private API, or it could also just be a mishap on the App Store server, so it's better to open tickets with Apple to correct this, and use Xcode 13 in the meantime.

    That said, if you have to use Xcode 14, and you don't use any iOS native plugins that may listen to the App's lifecycle, you can try renaming those plugin API interfaces into different names. I did a quick test with my project and it seem to run fine on my M1 Mac:
    upload_2022-9-18_15-33-47.png
     
    Last edited: Sep 19, 2022
    yuhuilalala likes this.
  5. tvalleau

    tvalleau

    Joined:
    Jul 1, 2010
    Posts:
    108
    Bump. I also am stuck being unable to upload my latest iOS version to the app store. Tried Neonlyte's solution, with no luck. I did submit a bug report to Apple, but I'd like to make sure the devs here see this too, just in case they have a solution, such as specifying public/private on these or at least take a look at it to ensure it's really an Apple problem and not a Unity one. Is there a way for me to directly report this, rather than hope they stumble across it in this forum?
     
  6. Sugarbear

    Sugarbear

    Joined:
    Jan 18, 2017
    Posts:
    2
    Got same problem with unity 2020.3.12 and Xcode 14.0.1

    The app references non-public selectors in Payload/AppName.app/Frameworks/UnityFramework.framework/UnityFramework: didReceiveRemoteNotification:, loadPlugin

    But it was loaded each time (5 times) so try check appstoreconnect testflight
     
    manaoneseok likes this.
  7. s1gh7

    s1gh7

    Joined:
    Oct 13, 2016
    Posts:
    12
    I have the exact same problem. Do you found a solution for it? I can't find any hints out there.
     
  8. Bersaelor

    Bersaelor

    Joined:
    Oct 8, 2016
    Posts:
    110
    I was able to successfully get a testflight app approved by following @Neonlyte 's above method.
    Good look getting apple to remove the false positive though.
     
  9. s1gh7

    s1gh7

    Joined:
    Oct 13, 2016
    Posts:
    12
    OK thanks, I will give it a try.
     
  10. Neonlyte

    Neonlyte

    Joined:
    Oct 17, 2013
    Posts:
    505
    In another post I also mentioned that I had success submitting a binary even without correcting the warnings. Probably you don’t actually have to do anything at the moment.
     
    siddharth3322 and Bersaelor like this.
  11. tvalleau

    tvalleau

    Joined:
    Jul 1, 2010
    Posts:
    108
    FWIW, I downgraded to XCode 13, and it compiled and uploaded without any issue.
     
    manaoneseok likes this.
  12. tnamikawa

    tnamikawa

    Joined:
    Mar 11, 2015
    Posts:
    1
    I still have this problem with 2021.3.11 and XCode 14.0.1.
     
  13. BurningthumbStudios

    BurningthumbStudios

    Joined:
    Apr 28, 2008
    Posts:
    95
    I ignored the error. Submitted the build and it was accepted and published by Apple.
     
  14. siddharth3322

    siddharth3322

    Joined:
    Nov 29, 2013
    Posts:
    1,042
    Though its given this kind of error dialog box during uploading but the build was uploaded successfully.
    hoops english non-public selectors.png

    Through Testflight I have sent it to multiple testers and it worked too.
    But I can't able to understand the meaning of this error.
     
    drewjosh likes this.
  15. notboring

    notboring

    Joined:
    Mar 1, 2014
    Posts:
    5
    I got that error as well. I am not able to release any IPA with that error on Test Flight or send it to Apple. I tried Neonlytes method but with no success.
     
  16. siddharth3322

    siddharth3322

    Joined:
    Nov 29, 2013
    Posts:
    1,042
    I am just in testing phase of the game so I don't have an issue.
    At publish time, I hope this error will get resolved.
     
  17. Wazii414

    Wazii414

    Joined:
    Mar 28, 2019
    Posts:
    3
    I ignored the error. Submitted the build and it was accepted and published by Apple.
    I hope this warning will be resolved soon
     
    Last edited: Feb 10, 2023
  18. nijingtech_DEV

    nijingtech_DEV

    Joined:
    Nov 6, 2019
    Posts:
    1
    Yes, although the same error was reported, the binaries were successfully uploaded and could be tested in TestFlight.
     
    pandolfini likes this.
  19. Jon_Wick

    Jon_Wick

    Joined:
    Jul 12, 2017
    Posts:
    9
    Hi, how do you upload builds to Test Flight? I upload using xCode and it stops right after the warning.
     
  20. mountainmarc1972

    mountainmarc1972

    Joined:
    Jun 17, 2017
    Posts:
    14
    In my case I saw the warning, but it did successfully upload to appstore connect. Just wait 10 minutes for the binary to process, then the build should be available for testflight.
     
  21. Jon_Wick

    Jon_Wick

    Joined:
    Jul 12, 2017
    Posts:
    9
    it works!
     
    pandolfini and mountainmarc1972 like this.
  22. drewjosh

    drewjosh

    Joined:
    Sep 24, 2019
    Posts:
    23
    I have XCode 14.0.1, same issue and thanks to @siddharth3322 I just waited it out and, Boom it still got uploaded. Thanks :)
     
    pandolfini and siddharth3322 like this.
  23. yuhuilalala

    yuhuilalala

    Joined:
    Nov 8, 2014
    Posts:
    7
    2019.4, Xcode 14.2 still have the issue.

    but I have find some clues:
    this function didReceiveRemoteNotification has been deprecated. Follow the doc of apple, there's a new method for fetching notifications.

    But my game have no need of notifications. I just disabled all implementation of didReceiveRemoteNotification.
     
    Last edited: Mar 30, 2023
    drewjosh likes this.