azun

I'm having the issue: `java.lang.NoClassDefFoundError` with SonarQube v10.5.1 and `community-branch-plugin` v1.19.0 ``` Exception in thread "Thread-0" java.lang.NoClassDefFoundError: ch/qos/logback/classic/spi/ThrowableProxy at ch.qos.logback.classic.spi.LoggingEvent.(LoggingEvent.java:145) at ch.qos.logback.classic.Logger.buildLoggingEventAndAppend(Logger.java:424) at ch.qos.logback.classic.Logger.filterAndLog_0_Or3Plus(Logger.java:386) at ch.qos.logback.classic.Logger.error(Logger.java:543) at org.eclipse.jgit.internal.util.ShutdownHook.cleanup(ShutdownHook.java:87) at java.base/java.lang.Thread.run(Thread.java:840)...

Thanks @gjabouley-invn I didn't know these were issues of SonarQube. I'll update as you suggested.

This can suppress the warnings: - https://stackoverflow.com/a/64842804/24658404 but it doesn't support versioned dependencies: - https://forums.swift.org/t/question-about-contains-unsafe-build-flags-in-spm/47677/4 About the root cause of the warnings: - https://forums.swift.org/t/root-cause-of-umbrella-header-for-module-does-not-include/24063/2 So to fix the warnings, we...

This also happens when running fastlane `scan` with `run_rosetta_simulator` turned on ``` xcodebuild: error: Unable to find a device matching the provided destination specifier: { platform:iOS Simulator, arch:x86_64, id:329FD16A-F95A-460D-BAB9-7F4CEA4793F5 }...

I managed to trigger the Rosetta simulator. with `xcodebuild`, adding the option `ARCHS=x86_64`: ``` xcodebuild ARCHS=x86_64 test \ -scheme "MyScheme" \ -project "./MyProject.xcodeproj" \ -destination "platform=iOS Simulator,OS=18.0,name=iPhone SE (3rd generation)"...

when specifying a device(name) for `xcodebuild`, there should be 2 simulators matching the name:Non-Rosetta and Rosetta. However, there's no way to specify the Rosetta one. and `xcodebuild` auto-picks the first...

Closing this issue, as it has been resolved

Thanks for the PR. Do we have a plan for merging this PR? I'm looking forward to using this support. 🙇

@DoHue97 when executing the lane, fastlane first built your app, however it failed to build your app. unfortunately, i don't know what caused the failure.