Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GCC_INSTRUMENT_PROGRAM_FLOW_ARCS in project file #95

Closed
vytautasgimbutas opened this issue Jan 11, 2017 · 4 comments
Closed

GCC_INSTRUMENT_PROGRAM_FLOW_ARCS in project file #95

vytautasgimbutas opened this issue Jan 11, 2017 · 4 comments

Comments

@vytautasgimbutas
Copy link

Hi,
i've tried submitting an app which recently has added SkyFloatingLabelTextField and I get an error:
http://stackoverflow.com/questions/34581925/xcode-do-not-submit-apps-with-gcc-style-coverage-ios-upload-processing-error

I see that you set GCC_INSTRUMENT_PROGRAM_FLOW_ARCS to YES in your project file which seems to me to be what's causing the issue.

@k0nserv
Copy link
Contributor

k0nserv commented Jan 11, 2017

How are you integrating the project? I suppose you are using manual integration since you are getting errors related to the project file? If so can you verify that changing the value for release to NO solves the problem?

@vytautasgimbutas
Copy link
Author

I'm integrating it via Carthage.
I can confirm that after changing the values to NO in release for constants GCC_GENERATE_TEST_COVERAGE_FILES, GCC_INSTRUMENT_PROGRAM_FLOW_ARCS, rebuilding the framework (without checking it out) I was able to upload successfully the binary to iTunes connect. I found that some people also got around this issue with setting bitcode to NO, but in my project it is set to YES and maybe that's why no one else encountered the problem yet.

I found this in Realm changelog, although not mentioned why, but I assume for the very same reason:

0.93.2 Release notes (2015-06-12)
=============================================================

### Bugfixes

* Fixed an issue where the packaged OS X Realm.framework was built with
  `GCC_GENERATE_TEST_COVERAGE_FILES` and `GCC_INSTRUMENT_PROGRAM_FLOW_ARCS`
  enabled.

@k0nserv
Copy link
Contributor

k0nserv commented Jan 12, 2017

Thanks, I'll change that an issue a new release.

@k0nserv
Copy link
Contributor

k0nserv commented Jan 16, 2017

This just went out in release 2.0.1. Thanks for reporting and helping find the fix @vytautasgimbutas

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants