9

I've uploaded a pure-Swift 2 binary to iTunes Connect, with hopes of distributing via Test Flight.

This should be possible, according to iTunes Connect itself:

enter image description here

Unfortunately, my binaries are met with an "Invalid Binary" error:

enter image description here

Obviously, I've tried this a few times. What hasn't worked:

The error I'm receiving via email is:

enter image description here

Which seems to suggest that the first screenshot, taken from iTunes Connect, is wrong. Have I gone crazy? (There are those who think we all have.)

Update: It would appear that some people can upload their iOS 9 betas. After running all of these attempts again, I am not one of those people.

Update: This is only happening with one of my apps. The only source or dependency difference between the two is that the failing app uses the Parse SDK Cocoapod.

Community
  • 1
  • 1
Patrick Perini
  • 22,555
  • 12
  • 59
  • 88

1 Answers1

2

Seems like the issue was the Parse SDK, which had an available update.

Ran pod update, then updated my code to compile against the updates in the SDK.

To address The files libswiftCoreLocation.dylib don’t match /Payload/My.app/Frameworks/libswiftCoreLocation.dylib specifically, I had to do some bundle trickery: https://stackoverflow.com/a/32535087/809150.

Community
  • 1
  • 1
Patrick Perini
  • 22,555
  • 12
  • 59
  • 88