Marco Masser

I also tried to install Danger Swift using SwiftPM, but no luck here. `swift build` runs fine and running `swift run danger-swift --help` prints the help just fine, but things...

Of course! ```swift // swift-tools-version:5.5 import PackageDescription let package = Package( name: "MyApp", dependencies: [ .package(url: "https://github.com/danger/swift.git", from: "3.12.3") ], targets: [ .target( name: "MyApp", dependencies: [.product(name: "Danger", package: "swift")],...

I have a tiny bit of progress to report: I tried this with a completely fresh Xcode project, added a `Package.swift` file with the above contents and did a `swift...

Just for clarification: Between steps, I manually deleted everything in `.build/` _except_ `checkouts`, `repositories`, and `workspace-state.json`. Also: I also tried using `platforms: [.macOS("12.1")]` instead of `platforms: [.macOS(.v12)]` with the same...

I just realized that when the problem seems to be that `arm64-apple-macosx12.0` is considered to be incompatible, that could mean that whatever is trying to load `libDanger.dylib` might not be...

Nice, this seems to work fine. Thank you very much for your help!

I don’t know if that helps you at all or not, but what @f-meloni wrote in https://github.com/danger/swift/issues/464#issuecomment-1006019283 is exactly how we use Danger-Swift on both Intel and Apple Silicon Macs...

FWIW, this started working again for us without further changes after the 11.0.5 release.

Looks good to me! Do we want to add some tests that stress encoding/decoding on multiple threads?

Thanks @balthisar for bringing this up. I’m one of the developers of [Little Snitch](//obdev.at/littlesnitch) and if anyone has any questions regarding the Internet Access Policy, I’m happy to answer them....