Posts

Post not yet marked as solved
0 Replies
870 Views
We are using slather to generate the coverage report. We do see sometimes we are getting issues when generating the coverage and it fails with below error. Based on the error , i see its comes from LLVM Failed to load coverage: Invalid instrumentation profile data (bad magic) error: Could not load coverage information /Users/**/.rvm/gems/ruby-2.7.0/gems/json-2.2.0/lib/json/common.rb:156: warning: Using the last argument as keyword parameters is deprecated /Users//.rvm/gems/ruby-2.7.0/gems/json-2.2.0/lib/json/common.rb:156:in `parse': 785: unexpected token at '' (JSON::ParserError) from /Users//.rvm/gems/ruby-2.7.0/gems/json-2.2.0/lib/json/common.rb:156:in `parse' from /Users//.rvm/gems/ruby-2.7.0/gems/slather-2.4.7/lib/slather/project.rb:135:in `pathnames_per_binary' from /Users//.rvm/gems/ruby-2.7.0/gems/slather-2.4.7/lib/slather/project.rb:124:in `block in profdata_coverage_files' from /Users//.rvm/gems/ruby-2.7.0/gems/slather-2.4.7/lib/slather/project.rb:123:in `each' from /Users//.rvm/gems/ruby-2.7.0/gems/slather-2.4.7/lib/slather/project.rb:123:in `profdata_coverage_files' from /Users//.rvm/gems/ruby-2.7.0/gems/slather-2.4.7/lib/slather/project.rb:98:in `coverage_files' from /Users//.rvm/gems/ruby-2.7.0/gems/slather-2.4.7/lib/slather/coverage_service/cobertura_xml_output.rb:18:in `post' from /Users//.rvm/gems/ruby-2.7.0/gems/slather-2.4.7/lib/slather/command/coverage_command.rb:97:in `post' from /Users//.rvm/gems/ruby-2.7.0/gems/slather-2.4.7/lib/slather/command/coverage_command.rb:59:in `execute' from /Users//.rvm/gems/ruby-2.7.0/gems/clamp-1.3.1/lib/clamp/command.rb:66:in `run' from /Users//.rvm/gems/ruby-2.7.0/gems/clamp-1.3.1/lib/clamp/subcommand/execution.rb:18:in `execute' from /Users//.rvm/gems/ruby-2.7.0/gems/clamp-1.3.1/lib/clamp/command.rb:66:in `run' from /Users//.rvm/gems/ruby-2.7.0/gems/clamp-1.3.1/lib/clamp/command.rb:140:in `run' from /Users//.rvm/gems/ruby-2.7.0/gems/slather-2.4.7/bin/slather:17:in `<top (required)>' from /Users//.rvm/gems/ruby-2.7.0/bin/slather:23:in `load' from /Users//.rvm/gems/ruby-2.7.0/bin/slather:23:in `<main>' from /Users//.rvm/gems/ruby-2.7.0/bin/ruby_executable_hooks:24:in `eval' from /Users/**/.rvm/gems/ruby-2.7.0/bin/ruby_executable_hooks:24:in `<main>' Has anyone seen that issue?
Posted Last updated
.
Post not yet marked as solved
0 Replies
379 Views
We are seeing issue when try to run the xcodebuild command using ssh, it fails but when running the same using VNC and open terminal app, it works. Anyone seeing the same issue. Any workaround and help is appreciated. Codesign and simulator all works well but fails when run the same commend using ssh. Error: found: Select a different signing certificate for CODESIGNIDENTITY, a team that matches your selected certificate, or switch to automatic provisioning.
Posted Last updated
.
Post not yet marked as solved
0 Replies
447 Views
Seeing issue with xcode12 when running with older xcode like 11.7 or 11.6. Xcode12 wiping out the older simulators and when running xcodebuild,it throw no simulator found error. watchOS 6.2 (6.2.1 - 17T531) - com.apple.CoreSimulator.SimRuntime.watchOS-6-2 (unavailable, failed to open liblaunchsim.dylib) ==> not available: Error Domain=com.apple.CoreSimulator.SimError Code=401 "The watchOS 6.2 simulator runtime is not available." UserInfo={NSLocalizedDescription=The watchOS 6.2 simulator runtime is not available., NSUnderlyingError=0x7fe6676e07a0 {Error Domain=NSPOSIXErrorDomain Code=53 "Software caused connection abort" UserInfo={NSLocalizedFailureReason=XPC error talking to SimLaunchHostService: <error: 0x7fff979c39a0> { count = 1, transaction: 0, voucher = 0x0, contents = "XPCErrorDescription" => <string: 0x7fff979c3b08> { length = 18, contents = "Connection invalid" } }}}, NSLocalizedRecoverySuggestion=Unable to open liblaunchsim.dylib. Try reinstalling Xcode or the simulator runtime., NSLocalizedFailureReason=failed to open liblaunchsim.dylib}, tvOS 13.4 (13.4 - 17L255) - com.apple.CoreSimulator.SimRuntime.tvOS-13-4 (unavailable, failed to open liblaunchsim.dylib) ==> not available: Error Domain=com.apple.CoreSimulator.SimError Code=401 "The tvOS 13.4 simulator runtime is not available." UserInfo={NSLocalizedDescription=The tvOS 13.4 simulator runtime is not available., NSUnderlyingError=0x7fe6a7704320 {Error Domain=NSPOSIXErrorDomain Code=53 "Software caused connection abort" UserInfo={NSLocalizedFailureReason=XPC error talking to SimLaunchHostService: <error: 0x7fff979c39a0> { count = 1, transaction: 0, voucher = 0x0, contents = "XPCErrorDescription" => <string: 0x7fff979c3b08> { length = 18, contents = "Connection invalid" } }}}, NSLocalizedRecoverySuggestion=Unable to open liblaunchsim.dylib. Try reinstalling Xcode or the simulator runtime., NSLocalizedFailureReason=failed to open liblaunchsim.dylib}, iOS 13.5 (13.5 - 17F61) - com.apple.CoreSimulator.SimRuntime.iOS-13-5 (unavailable, failed to open liblaunchsim.dylib) ==> not available: Error Domain=com.apple.CoreSimulator.SimError Code=401 "The iOS 13.5 simulator runtime is not available." UserInfo={NSLocalizedDescription=The iOS 13.5 simulator runtime is not available., NSUnderlyingError=0x7fe6a77076a0 {Error Domain=NSPOSIXErrorDomain Code=53 "Software caused connection abort" UserInfo={NSLocalizedFailureReason=XPC error talking to SimLaunchHostService: <error: 0x7fff979c39a0> { count = 1, transaction: 0, voucher = 0x0, contents = "XPCErrorDescription" => <string: 0x7fff979c3b08> { length = 18, contents = "Connection invalid" } }}}, NSLocalizedRecoverySuggestion=Unable to open liblaunchsim.dylib. Try reinstalling Xcode or the simulator runtime., NSLocalizedFailureReason=failed to open liblaunch_sim.dylib}, ] when matching for <IBCocoaTouchPlatformToolDescription: 0x7fe667469930> System content for IBCocoaTouchFramework-ThirteenAndLater <IBScaleFactorDeviceTypeDescription: 0x7fe66745b410> scaleFactor=2x, idiom=<IBIPhoneIdiom: 0x7fe667486830> runtime=<IBCocoaTouchTargetRuntime: 0x7fe697635f10> /* com.apple.actool.compilation-results */
Posted Last updated
.