My app binary became "Invalid Binary.", after submitted.

[08/03, 2022]

English / 日本語

Hello, I'm Tomo.

Shortly after submitting my iOS app for review, I received an email saying "Invalid Binary."

I looked at AppstoreConnect while wondering why, but the reason was not written at all, and when I looked at the email, I received the following email.

ITMS-90433: Invalid Swift Support - The file libswiftAVFoundation.dylib doesn't have the correct code signature. Make sure you're using the correct signature, rebuild your app using the current public (GM) version of Xcode, and resubmit it. Don't just modify the code signature of libswiftAVFoundation.dylib.

When I googled it, other people wrote various reasons why the AppClip settings were empty, and I couldn't find the "libswiftAVFoundation."

In the first place, "libswiftAVFoundation.dylib" is supposed to be Apple's genuine library, so why is that strange? I was pretty confused.

The cause is that the project was opened with the beta version of Xcode (probably)

At first, I thought that I was doing something with the Firebase and AdMob libraries, but I didn't find any articles.

I just remembered, "I opened the project with the beta version of Xcode". But I had no idea to fix it even if it's the true cause.

So I just tried as much as I can like these below,

  • Delete .xcworkspace (because I use cocoapods)
  • Delete Podfile.lock
  • Delete Pod folder
  • Delete Xcode cache > ~/Library/Developer/Xcode/DerivedData
  • After deleting the above, install pod again with pod update and generate .xcworkspace

After I did them all and submitted a new binary on the AppstoreConnect again. After a while, it passed the review without any "Invalid Binary." notification!

Perhaps, just regenerating .xcworkspace seems to be good, but it takes time to try once, so I tried everything 😂

Anyway, I got a happy ending.