Closed kaosdg closed 6 years ago
It seems to me as this is entirely Carthage issue or something that is not officially supported, but test coverage is something that can be sacrificed, so no need for extra scheme, it can be just turned off. Done in 33993df68a332c1748e8e16d5d977eb69eb879c0
... and add a new Testing scheme that has code coverage.
We're currently using Carthage static frameworks (https://github.com/Carthage/Carthage/blob/master/Documentation/StaticFrameworks.md) in our applications to increase app load times.
However, when Carthage builds Dip for static frameworks, the code coverage option on the Dip scheme leads to the following errors:
By disabling code coverage on the scheme that Carthage builds, this issue is resolved.
I've added a separate Scheme solely for tests that enables code coverage, and adjusted the .travis.yml settings to use that.