Problem no coverage directory found at Bitrise

[Vinicius Mangueira]

Hi Greetings,

When we run a command slather coverage --sonarqube-xml from local way, we have with success output, but when we run the same command at CI after run tests cases at Bitrise is:

/Users/vagrant/git/vendor/bundle/ruby/2.6.0/gems/slather-2.7.1/lib/slather/project.rb:239:in `profdata_coverage_dir': No coverage directory found. (StandardError)
	from /Users/vagrant/git/vendor/bundle/ruby/2.6.0/gems/slather-2.7.1/lib/slather/project.rb:517:in `find_binary_files'
	from /Users/vagrant/git/vendor/bundle/ruby/2.6.0/gems/slather-2.7.1/lib/slather/project.rb:456:in `configure_binary_file'
	from /Users/vagrant/git/vendor/bundle/ruby/2.6.0/gems/slather-2.7.1/lib/slather/project.rb:336:in `configure'
	from /Users/vagrant/git/vendor/bundle/ruby/2.6.0/gems/slather-2.7.1/lib/slather/command/coverage_command.rb:59:in `execute'
	from /Users/vagrant/git/vendor/bundle/ruby/2.6.0/gems/clamp-1.3.2/lib/clamp/command.rb:66:in `run'
	from /Users/vagrant/git/vendor/bundle/ruby/2.6.0/gems/clamp-1.3.2/lib/clamp/subcommand/execution.rb:18:in `execute'
	from /Users/vagrant/git/vendor/bundle/ruby/2.6.0/gems/clamp-1.3.2/lib/clamp/command.rb:66:in `run'
	from /Users/vagrant/git/vendor/bundle/ruby/2.6.0/gems/clamp-1.3.2/lib/clamp/command.rb:140:in `run'
	from /Users/vagrant/git/vendor/bundle/ruby/2.6.0/gems/slather-2.7.1/bin/slather:17:in `<top (required)>'
	from /Users/vagrant/git/vendor/bundle/ruby/2.6.0/bin/slather:23:in `load'
	from /Users/vagrant/git/vendor/bundle/ruby/2.6.0/bin/slather:23:in `<main>'
No coverage directory found.
	Are you sure your project is generating coverage? Make sure you enable code coverage in the Test section of your Xcode scheme.
	Did you specify your Xcode scheme? (--scheme or 'scheme' in .slather.yml)
	If you're using a workspace, did you specify it? (--workspace or 'workspace' in .slather.yml)
	If you use a different Xcode configuration, did you specify it? (--configuration or 'configuration' in .slather.yml)

I try a lot a things to solve this problem, everything works fine but in CI the problem has not solved yet