Xcode 12.5 on macOS 12: Code signing "MyAppExtension.appex" failed.

Signing code on macOS 12 with Xcode 12.5 doesn’t work properly for my iOS app.. a few seconds earlier the macOS App was signed properly.

Xcode 13 also signs it properly.

Feedback filed: FB9134464

(booting back to Big Sur solves it for now...)

Up vote post of LH16 Down vote post of LH16
4.1k views
Posted by
LH16
Reply

  • have the same issue 😦

    —
    Katcinskiy

  • Can you please share how to boot back to big sure?

    —
    Katcinskiy

  • Same here

    —
    batschz

Replies

Seeing the same thing here. I'll dupe your FB.

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

Having the exact same issue!

Posted by
AppMent
Up vote reply of AppMent Down vote reply of AppMent

  • I believe I'm having the same issue with code signing, can you go into more specifics?

    I'm unable to upload watch apps to App Store connect, the extension fails code signing- the same with a known to work iOS application which up until the update to Monterey was signing just fine,

    —
    JIMMWX

  • It's the exact same thing I'm experiencing, but it's all the Xcode projects. I have tried to create new project and I get the same code signing error, I have tried existing projects it's the same. I think it's not related to the Xcode projects, but something in macOS 12 that does not comply correctly with the Xcode 12 application. I will try in Xcode 13 beta 1 now and see if that changes anything.

    —
    AppMent

  • Not working with any versions of Xcode, this is really not good 😅

    —
    AppMent
Add a Comment

Updating to Xcode 13 Beta solves the issue perfectly. If you are on macOS 12 Monterey Beta please update to Xcode 13 Beta.

Posted by
StepanRumyantsev
Up vote reply of StepanRumyantsev Down vote reply of StepanRumyantsev

  • You can't submit a build from Xcode 13 beta (no beta Xcode's allowed) to review.

    —
    LH16

  • Yes, unfortunately I've just figured this out trying to submit an app update.

    —
    StepanRumyantsev

  • The archive successfully signed and uploaded in Xcode 13.0 beta (13A5154h). Can I expect it will be accepted in review if the archive generation happened with the public Xcode, but the upload happened with Xcode beta? What about for TestFlight, but publicly and internally?

    —
    Curiosity
Add a Comment

Confirmed as working if you update to Xcode 13 Beta 1.

Curiosity - you can upload from Xcode 13 to App Store connect, but for internal testing/testflight only. If you try to submit it to the App Store it will get rejected. Even if you build it with Xcode 12.5 and upload with 13 as it will sign it with Xcode 13 (I had this issue last year with Xcode 11 built, Xcode 12 Beta upload)

Hopefully Apple will resolve this soon :-)

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

I've made a small research and it appears that based on what's happened in the past you can't release production apps to App Store from either beta macOS or beta Xcode. Such apps will be rejected during the review. That makes a little bit of sense to me.

Still I solved the problem for myself with very little pain preserving the macOS Monterey Beta installation. Here is the solution (a bit verbose):

  • Download macOS Big Sur from App Store (right from your macOS Monterey Beta). The download link could be found here: https://support.apple.com/en-us/HT201372. No need to create a bootable USB flash. Just click the link and the Big Sur installer will start-up automatically when the download is finished;
  • While downloading go to the Disk Utility and create a new partition where you can put your Big Sur (consult Google if in doubt, keywords - dual boot macOS);
  • While downloading copy your Keychains folder from your macOS Monterey Beta (Finder -> Go -> Hold Option/Alt to reveal hidden items and select Library and then locate the Keychains folder) to a USB stick. You would need it in macOS Big Sur. Copy your coding project folders or other important files to the same USB if needed;
  • Once Big Sur download is done and the installer opens up - simply install it onto the newly created partition. Right from macOS Monterey Beta;
  • Once the Big Sur installer asks for a restart - get ready to hold the Option/Alt key upon system startup to select the Big Sur partition as boot device. Alternatively you can just change it in System Preferences -> Startup disk in right from macOS Monterey Beta;
  • Once the Big Sur installation is done - copy the stored Keychains folder you saved before from Monterey to the same location in Big Sur.

Thank you!

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

Seems to be fixed with macOS Monterey Beta 3

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

  • The same for me, thank you for notification.

    —
    Katcinskiy
Add a Comment