-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue on linking Mocker while building on device or archiving #75
Comments
I'm on Xcode 12.3: Getting the same issue on version 2.4.0 and 2.2.0 - I can build on simulators, but get the error above when building on my device (Iphone 11 pro). This might be part of a much larger issue: ReactiveX/RxSwift#2127. |
I've not been able to find the cause of this. We're running the project on Xcode 12.3 without any issues, even on a device 🤔 |
I'm seeing the same issue, even building for simulator, using Xcode 12.2/12.3 and Mocker 2.4.0. Switching to Mocker 2.2.0 allowed my project to compile as well. |
This issue is stale because it has been open for 30 days with no activity. Remove the Stale label or comment or this will be closed in 10 days. |
I had the same issue. Switching to Mocker 2.2.0 fixed it |
I really wonder how this is happening to you. We're using the latest version of Mocker in all our projects at WeTransfer and we never run into this error. Can you share which Xcode version you're using and how you integrated Mocker? |
Can confirm it's still happening on my machine: Spec: Reverting to Mocker 2.2.0 solved the issue func test_OK() {
let configuration = URLSessionConfiguration.af.default
configuration.protocolClasses = [MockingURLProtocol.self]
let sessionManager = Alamofire.Session(configuration: configuration)
let originalUrl: URL = URL(string: "Some URL")!
let mock = Mock(url: originalUrl, contentType: .json, statusCode: 200, data: [.post: <Some Data here>])
mock.register()
let expectation = XCTestExpectation(description: "Create JSON")
Task {
// Call application code here //
}
wait(for: [expectation], timeout: 5.0)
} |
@nurkenn-keda you've shared code that looks good. What issue are you actually facing? |
This is likely caused by the 2.3.0 release, more specifically this PR.
The text was updated successfully, but these errors were encountered: