You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have read CONTRIBUTING and have done my best to follow them.
What did you do?
We run following spec for macOS platform:
it("should NOT be called") {
expect(subject.removeAccounts()).to(throwAssertion())
}
Note: subject.removeAccounts does assertionFailure("should not be called")
What did you expect to happen?
Spec is passed.
BTW, we see this behavior in Nimble 13.0.0
What actually happened instead?
Spec is crashed.
Console has message
Note: throwAssertion no longer works on tvOS or watchOS platforms when you use Nimble with Cocoapods.
You will have to use Nimble with Swift Package Manager or Carthage.
It looks like arch or canImport is incorrectly resolved in ThrowAssertion.swift
Environment
List the software versions you're using:
Quick: 7.3.0
Nimble: 13.1.1
Xcode Version: Version 15.0.1 (15A507) (Open Xcode; In menubar: Xcode > About Xcode)
Swift Version: Default (Open Xcode Preferences; Components > Toolchains. If none, use Xcode Default.)
MacOS: 14.1.2.
Please also mention which package manager you used and its version. Delete the
other package managers in this list:
Cocoapods: 1.14.3 (Use pod --version in Terminal)
The text was updated successfully, but these errors were encountered:
What did you do?
We run following spec for macOS platform:
Note: subject.removeAccounts does
assertionFailure("should not be called")
What did you expect to happen?
Spec is passed.
BTW, we see this behavior in
Nimble 13.0.0
What actually happened instead?
Spec is crashed.
Console has message
It looks like
arch
orcanImport
is incorrectly resolved inThrowAssertion.swift
Environment
List the software versions you're using:
Xcode Default
.)Please also mention which package manager you used and its version. Delete the
other package managers in this list:
pod --version
in Terminal)The text was updated successfully, but these errors were encountered: