6

This only happens post app store upload and during processing.

Relevant settings for all targets:

CLANG_ENABLE_CODE_COVERAGE = NO GCC_INSTRUMENT_PROGRAM_FLOW_ARCS = NO

enter image description here enter image description here Can someone point to a config setting that could resolve this very recent issue with Xcode Version 7.2 (7C68)? Uploads have been fine until this point and no related config changes have been made.

The specific error:

Dear developer,

We have discovered one or more issues with your recent delivery for "The App Name". To process your delivery, the following issues must be corrected:

Invalid Bundle - Do not submit apps with GCC-style coverage instrumentation enabled. Specifically, the following Xcode build settings should be disabled: Instrument Program Flow Generate Test Coverage Files

Once these issues have been corrected, you can then redeliver the corrected binary.

Regards,

The App Store team

Improve this question
7
  • What are the build settings for "Generate Test Coverage Files" and "Generate Profiling Code"? Commented Jan 4, 2016 at 2:40
  • "Generate Test Coverage Files" does not exist, only "Generate Legacy Test Coverage Files" set to NO. Commented Jan 4, 2016 at 5:06
  • "Generate Profiling Code" is set to NO. Commented Jan 4, 2016 at 5:07
  • Sounds like a problem on their end. Maybe use a Technical Support Incident if you're not getting anywhere. Commented Jan 4, 2016 at 5:12
  • I'm having the same issue. Commented Jan 15, 2016 at 16:32

2 Answers 2

Reset to default
1

To work around this issue I set "Enable Bitcode" to "No" at the project level, which was it was previously set to and the last known good setting.

Improve this answer
Sign up to request clarification or add additional context in comments.

1 Comment

Note that the recommended setting for this is is YES. > Bitcode is an intermediate representation of a compiled program. Apps you upload to iTunes Connect that contain bitcode will be compiled and linked on the store. Including bitcode will allow Apple to re-optimize your app binary in the future without the need to submit a new version of your app to the store. developer.apple.com/library/tvos/documentation/IDEs/Conceptual/…
1

There are two relevant settings which should be NO for the Release configuration:

GCC_GENERATE_TEST_COVERAGE_FILES = NO;
and
GCC_INSTRUMENT_PROGRAM_FLOW_ARCS = NO;

Or in Xcode, under Build Settings > Apple LLVM 7.0 - Code Generation

Xcode Settings

I found that the Enable Code Coverage Support (CLANG_ENABLE_CODE_COVERAGE) is not required to be disabled. Vanilla Xcode projects have this enabled by default.

Also, of course you only need to make sure that the GGC settings are disabled for the Release configuration, assuming that's used for Archive.

3rd party frameworks

Finally note that if your project includes any 3rd party frameworks, all of these frameworks also need to be build using the above settings.

Unfortunately Apple iTunes Store's email doesn't tell you which project or framework failed, so debugging this might involve some trial and error.

Improve this answer

1 Comment

Interesting. I did try both the GCC_GENERATE_TEST_COVERAGE_FILES = NO; and GCC_INSTRUMENT_PROGRAM_FLOW_ARCS = NO;, but I did not check them for the 3rd party frameworks. Changing those settings represents other challenges so I may need to stick to the Enable Bitcode approach for now.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.