Closed skyylex closed 4 years ago
For anyone blocked by this, the recent 2.0 release seems to've fixed the issue for me. I was pulling in this library via Quick and Nimble, which haven't updated to 2.0 yet (even after six whole hours! 😛 ), so I just added this library directly:
Hats off to the developers!
Yes, if you're using Quick/Nimble, pull the master
branch since the update to fix this problem (update CwlPreconditionTesting 2.0.0-beta.1 or newer) is on master but is not part of the latest (8.0.4) release.
FYI, I believe this issue is due to an Xcode bug around the SWIFT_PACKAGE
macro (although it's not totally clear since there's been no response on the Feedback). In any case, CwlCatchException 2.0.0-beta.1 and greater (incl. 2.0.0) works around the issue by removing the macro entirely:
https://github.com/mattgallagher/CwlCatchException/commit/b1b53c1d6eedf39555745fa7f6a70c99177883ba
tl;dr pull CwlPreconditionTesting 2.0.0-beta.1 or newer (incl. 2.0.0) you'll get the fix.
Hi,
From time to time I'm facing the following issue when building the Tests target that uses
catchBadInstruction { }
fromCwlPreconditionTesting
.Xcode build log:
Environment:
Used versions: