无法从框架内访问公共枚举

Question

I have been working on developing a framework and I have decided to create custom enums that extend the Error protocol to report to the host application when a domain specific error is encountered.

ie

public enum MyCustomError: Error {
    case customCase(message: String)
}

from the host application I have a response call back that is another enum with associated value

ie

public enum MyCustomResponse {
    case success
    case error(Error)
}

form within the host application I try to access the error by doing the following

ie

let responseHandler: (MyCustomResponse) -> Void = { response in

    switch response {
        case .error(let error):
            if case let MyCustomModule.MyCustomError.customCase(theErrorMessage) = error {
                print(theErrorMessage)
            }
    }
}

what I am getting is a message from the compiler telling me that MyCustomModule has no member named MyCustomError . If a loose the MyCustomModule. then the compiler complains Use of unresolved identifier 'MyCustomError' . I am importing MyCustomModule , and the access level of the MyCustomError is public , any ideas on how to solve this would be really appreciated.

Thanks

Note: I am developing my framework via cocoapods version 1.1.1 and using Xcode 8.2.1, swift version 3.0.2, supporting iOS version 8.0 and above.

Generated interface

import Foundation 

public enum MyCustomError : Error { 
    case customCase(message: String) 
}

Answer 1

After a long while trying out every little thing I could think of, even sandboxing the problem in a new repo (check github.com/anuragajwani/framework_pod_enums_test) without the ability to reproduce it I ended re-cloning the repository with the issue in question and reapplied all the changes and it worked no problem. Pitty I could not find the underlying problem, but by comparing each configuration setting in comparison with the sandboxed project and everything matching exactly I gave up. I have hunch that it had to with the compiler which given how flaky it is it would be no surprise.

Answer 2

I had the exact same issue. In my case I just set the "Build Active Architecture Only" to "No" in the Build Settings and the issue was gone.