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
  3. Join us on November 16th, 2023, between 1 pm and 9 pm CET for Ask the Experts Online on Discord and on Unity Discussions.
    Dismiss Notice

ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing

Discussion in 'iOS and tvOS' started by cmersereau, Jul 13, 2021.

  1. cmersereau

    cmersereau

    Joined:
    Nov 6, 2020
    Posts:
    52
    My team and I have a cloud build configuration that pushes the build to the Apple app store for TestFlight distribution. Our configuration has worked successfully for over a hundred builds, but we've suddenly got an email from Apple regarding an issue with our build, image attached.

    This build had some changes to the project that allowed us to support CocoaPod installation with the Facebook and Google Sign-in packages made for Unity. Even acknowledging this, I don't understand this issue and can't find anything about it on these forums.

    Since our builds are being made on the cloud and being uploaded to TestFlight from there, I'm having a hard time understanding what we can do to fix this or why it's happening in the first place if it's a requirement from Apple.
     

    Attached Files:

  2. Code-ttt

    Code-ttt

    Joined:
    Oct 20, 2014
    Posts:
    9
    Running into this issue now. Did you ever get this resolved?
     
  3. Code-ttt

    Code-ttt

    Joined:
    Oct 20, 2014
    Posts:
    9
    Alright, figured out our issue. The supplied error was not accurate. Had provided an Adhoc provisioning profile in the Unity Cloud Build. Changed it to an App store provisioning profile and the App Store processing step completed successfully.
     
  4. cmersereau

    cmersereau

    Joined:
    Nov 6, 2020
    Posts:
    52
    Can I ask if your cloud builds were working prior to provisioning profile fix? As in, if you installed directly from UCB instead of TestFlight, did the game run properly?

    For us, we get the ITMS error about the SwiftSupport folder, but when we run the corresponding cloud build the game actually crashes immediately on launch, so we know the build is missing something in the code.
     
  5. Code-ttt

    Code-ttt

    Joined:
    Oct 20, 2014
    Posts:
    9
    We were able to install and run the builds from UCB that were using the Adhoc provisioning profile without issue. This is with a project that has some Swift code in the Plugins folder that we are calling to do some authentication. And we have a Pods dependency that we need that the Swift plugin code calls.
     
  6. andersemil

    andersemil

    Joined:
    Feb 2, 2015
    Posts:
    107
    We are getting this error with Facebook SDK for Unity 11.0.0. We build an ad-hoc IPA in Unity Cloud Build and test it, and then we used to be able to just re-sign it using a modified version of https://github.com/RichardBronosky/ota-tools/blob/master/ipa_sign. But now we are getting the ITMS-90426 error when uploading, because Facebook SDK now depends on a lot of swift libraries, and the SwiftSupport folder is not generated in UCB for some reason :(

    I tried modifying the re-signing script to copy the SwiftSupport modules from XcodeDefault.xctoolchain, but then App Store Connect complains about the swiftmodules not having a signing ID. And codesign won't sign the swiftmodules.

    Pretty stumped at this.
     
    Last edited: Oct 6, 2021
  7. cmersereau

    cmersereau

    Joined:
    Nov 6, 2020
    Posts:
    52
    Did your UCB builds for iOS work with this attempted fix? We would be pretty stoked just to have working iOS builds on UCB again. If so, can you explain more or share some code about how you copy SwiftSupport modules from XcodeDefault.xctoolchain?