Comment by Marián Černý (JIRA)

This issue is not fixed yet. Tested in Swift 4.2 Xcode 10.0.

Framework A:

public class Magazine {}

Framework B:

public class Magazine {}

Application:

import A

import B

class B {}

class C {

{{ var magazine: B.Magazine?}}

{{}}}

This produces an error: 'Magazine' is not a member type of 'B'

The problem is that there is a type B named the same name as the framework B.

A possible workaround is to create `public typealias B_Magazine = Magazine` inside the framework B and use `B_Magazine` instead of `B.Magazine`.

Comment by Marián Černý (JIRA)

Similar problem.

I have a framework Reachability which has a class named Reachability.

I want to create my own wrapper class Reachability inside the App and use the Reachability from the framework inside the class.

Framework Reachability:

class Reachability { … }

Application:

import Reachability

class Reachability {

{{ let reachability = Reachability.Reachability()}}

{{}}}

Same error message: Type 'Reachability' has no member 'Reachability'

Possible workaround is to add `typealias FrameworkReachability = Reachibility` inside the framework (but I don’t want to change the framework) or rename Application’s Reachability for example to MyReachability (which I don’t like, because each module has it’s own namespace and there is no other type Reachability in the app).

A possible solution could be allowing renaming the imports, such as:

import Reachability as FrameworkReachability

Comment by Artem Loenko (JIRA)

This is still the case with Xcode 11.2 (11.2.1 GM). And we have some issues due to the problem. I think this one is quite important due to the fact that we have the module stability now, and a lot of 3rd party libraries started to adopt BUILD_LIBRARY_FOR_DISTRIBUTION option.

Any progress on that issue ? It is frankly a very weird limitation. it is not uncommon for modules to contain a public class of the same name as the module..

+1 same probrom