-
Notifications
You must be signed in to change notification settings - Fork 238
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
Coverage.profdata not found - Xcode 14.3 - Xcode 15.0 #541
Comments
News on this issue on Xcode 14.3 and 14.3.1? thanks |
News? I tried also on Xcode 15 and GitHub, but I got the same error |
With Xcode 14.2
With Xcode 14.3.x or Xcode 15
No one on this issue? @ksuther @marklarr thanks |
@salvatoreboemia I am having the same error, do you manage to solve it? |
Not able to manage... I removed slather step If you will find a fix please update this post. Thanks |
Before you do anything with your CI configuration please make sure that Xcode generates coverage report locally, in our case we didn't have this file generated, so it's not a surprise that slather did fail. Please try to check build logs or test report (depending on the Xcode version you're using) if you can find similar error to this one
If this is a case then solution described bellow might help you, I really hope it does. 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:
In our project We also tried to change 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. |
I'm also facing this issue with Xcode 15.0 and 15.1. Would love to hear of a solution to this issue.. |
The solution is to make sure ALL of your upstream dependencies have been built with XCode 14.3 or newer. If ANY of your deps is not built with XCode 14.3 or newer, the .profraw file will be corrupt, so lldb-profdata will be unable to create a .prodata file for slather to parse. |
I am currently facing the same issue. Any update on when this could get resolved? |
@edward-sentongo Are you 100% sure it's not #541 (comment) ? Does XCode show coverage % for all of the files you care about?
|
@jarrodlombardo-EventBase Xcode does show code coverage percentages for those files. |
We decided to build everything ourselves without using Slather. |
Issue Description
I upadated on GitHub my pipeline in order to use latest version of macOS and Xcode (13 and 14.3), but the slather scan failed (only with new macOS and Xcode version)
Command executed
Complete output when running fastlane, including the stack trace and command used
Environment
GitHub Env
Do you have any suggestions in order to fix this issue on GitHub and fastlane?
Thanks a lot
The text was updated successfully, but these errors were encountered: