Unable to upload iOS update after adding Flurry Analytics? Error: Your app can’t contain standalone executables or libraries
Asked Answered
C

3

16

In my Swift iOS application I've just added Flurry Analytics by creating a briding-header.h and importing Flurry.h. I then added SystemConfiguration.framework, CFNetwork.framework, and Security.framework.

I then added libFlurry_6.5.0.a via Targets -> Build Phases -> Link Binary with Libraries after instruction from a Stack Overflow question because it wouldn't build.

After archiving the app I tried to upload it and received this error:

ERROR ITMS-90171: “Invalid Bundle Structure - The binary file ‘APPNAME.app/Flurry/libFlurry_6.5.0.a’ is not permitted. Your app can’t contain standalone executables or libraries...

Coccidioidomycosis answered 24/5, 2015 at 1:5 Comment(0)
B
19
  1. Open the Build Phases tab in the target settings for your project.
  2. Make sure that Flurry.framework is not included under Copy Bundle Resources.

From Invalid Bundle Structure.

Bair answered 24/5, 2015 at 1:18 Comment(1)
Faced same issue. Added OCMock libs for unit test in test target but it was there in Copy Bundle Resource for all other targets. Can you please explain? @Daniel StormEasiness
S
0

I had the same problem of a different cause:

My project did depend on multiple c++ libraries, which I added to my Xcode project, but only as reference. Then I linked the .a files in Link Binary With Libraries build phase, which works for building and running the project, but throws this error when uploading to the App Store.

I fixed it with deleting the references in my project, and copying the files to my project instead (When adding files to the project, check the mark on "Copy items if needed"). After that I was able to upload my app.

Snocat answered 13/2 at 14:22 Comment(0)
L
-2

My case was a bit different. I added an static library to "Embed Frameworks" and I got a couple of errors when I uploaded the app to the app store:

  1. The binary X is not permitted. Your app can't contain standalone executables or libraries, other than a valid CFBundleExecutable of supported bundles
  2. Invalid Swift Support - Doesn't have the correct file type for this location

I removed this dependency and the problem was solved

Lithesome answered 3/10, 2018 at 12:40 Comment(2)
If your app needs the dependency, then how is this a valid solution?Aquinas
yeah this answer doesn't make senseBaldridge

© 2022 - 2024 — McMap. All rights reserved.