Did anyone solved the issue? We're also facing same issue after migrating from XCode 14.2 to 15.0.1. Interesting fact that this happens only to one of the our projects, another projects generates coverage report just fine.
vadimkrutov_lv
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Post
Replies
Boosts
Views
Activity
We spent really a lot of time debugging this, it appears that one of our dependencies was a binary (xcframework), most probably distributed via older version of the XCode, after updating this dependency coverage was back.
We spent a lot of time debugging this problem, but none of the suggestions we found helped.
it appears that one of our dependencies was a binary (xcframework), most probably distributed via older version of the XCode, after updating it coverage was back.
We spent a lot of time debugging this problem, but none of the suggestions we found helped.
We tried to update our Podfile with these settings:
config.build_settings['CLANG_ENABLE_CODE_COVERAGE'] = 'NO'
config.build_settings['swiftc'] = '$(SRCROOT)/SWIFT_EXEC-no-coverage'
In our project Instrument Program Flow & Generate Legacy Test Coverage build settings were already set to NO
We also tried to change Mach-O type for our cocoa pods dependencies to **static library ** and many other things.
it appears that one of our dependencies was a binary (xcframework), most probably distributed via older version of the XCode, after updating it coverage was back.