Seems related to how Carthage builds frameworks, although I suspect something else is going on here. Again I don't see any harm in changing this flag for Release builds as it shouldn't be relevant anyway. Frankly I'm not sure why the default is Yes for Release anyway.
This PR Fixes #262
We have not run into this issue yet, but I see no harm in turning this off for Release builds. There is some chatter online about this:
http://blog.carlossless.io/xcode-9-and-carthage-coverage-data
Seems related to how Carthage builds frameworks, although I suspect something else is going on here. Again I don't see any harm in changing this flag for Release builds as it shouldn't be relevant anyway. Frankly I'm not sure why the default is
YesforReleaseanyway.