My test keeps crashing `EXC_BAD_ACCESS`

[Boowman]

import Foundation
import Mockable

@Mockable
protocol TestProtocol {
    func testing(val: String) -> String
}

class TestService: TestProtocol {
    func testing(val: String = "") -> String {
        return "Testing"
    }
}

class TestViewModel: ObservableObject {
    private var services: TestProtocol
    private var value: String = ""

    init() {
        services = TestService()
        value = services.testing(val: "Some cool")
    }

    convenience init(services: TestProtocol) {
        self.init()
        self.services = services
        self.value = services.testing(val: "Whyyy")
    }

    func getValue() -> String {
        return value
    }
}

I have imported MockableTest into my test file, I have added MOCKING under Custom Flags for Debug and I added Mockable into my main target.

[Kolos65]

I cant reproduce this, your example is working fine on my end... Can you share your full test case? Do you always get BAD_ACCESS or just every other run?

[Boowman]

I get it every run, I tried it in a blank project, same issue. If it helps I can upload a Github repo and share it with you as it doesn't really make sense why it would crash to be fair.

[Kolos65]

Please send me a link to an example project, I still cannot repro this. What version of Xcode are you using?

[Boowman]

Link to a test project: https://github.com/Boowman/PlayWorld I am running Xcode 15.2, tested it on 15.0 and I get the same thing.

[Kolos65]

I found it:

Under the General settings of your PlayWorldTests target, go to Frameworks and Libraries and remove Mockable (keeping MockableTest).

MockableTest also includes Mockable so you only need to add MockableTest to your test targets. See the docs for more info.

[Boowman]

Well, I have good news and bad news:

• Good news is that you are right Mockable shouldn't have been added to the test target, not sure how it got there. Once I removed it it worked.
• Bad news is that I checked my main project and it still fails, double double-checked to make sure the package is only added where it should be. I know there's not much more you can do since I can't send over this one but I will keep looking and update this issue with what I find.

[Kolos65]

clean + reset packages cache + delete derived data + reopen xcode

[Boowman]

That did not seem to work, I am wondering if there is something I have to have enabled. I remember in other new projects I would get a popup on the side to allow macros. I didn't get it this time as it was an older project.

If I expand the macro I can see it getting created so I doubt it has anything to do with Allow & Trust