Xcode 12 different definitions in different modules build error

App & System Services General
mike-velu OP
Created Aug ’20
Replies 44
Boosts 1
Views 23k
Participants 37
In the Xcode 12 betas I'm seeing an issue with importing Swift modules with @objc annotations.

Given two Swift modules which expose classes of the same name:

Code Block 
// FrameworkOne
@objc
public class Thing: NSObject {
    public override init() {}
    @objc
    public func doSomething() {}
}


Code Block 
// FrameworkTwo
@objc
public class Thing: NSObject {
    public override init() {}
    @objc
    public func doSomethingElse() {}
}


And if I have imported both of the frameworks into an ObjC file and interact with the classes in either of them:

Code Block 
#import <Foundation/Foundation.h>
@import FrameworkOneObjC;
@import FrameworkTwoObjC;
@interface Example : NSObject 
@end
@implementation Example
- (void) example
{
    Thing *thing = [[Thing alloc] init];
}
@end


Then I'm seeing this build error:
Code Block 
'Thing' has different definitions in different modules; first difference is definition in module 'FrameworkOne.Swift' found method name 'doSomething'
But in 'FrameworkTwo.Swift' found method name 'doSomethingElse'


Is this expected behaviour? If so, is there any way to opt out?

In my case FrameworkOne & FrameworkTwo are external dependencies, and I'm unable to change the names of the classes.
Replies  44
Boosts  1
Views  23k
Participants  37
tuncerfromnull OP
Aug ’20
Same issue for me, we have got 2 different pods which contain same class names.
From Xcode 12 beta 5, the project can't compiled and gives same build error:
'X' has different definitions in different modules; first difference is definition in module 'Y' found method name 'Z'

I think that build process has been changed at Xcode 12 beta 5. I'm looking for a solution.
1
yuriyp OP
Aug ’20
Also seeing this issue in Xcode 12 beta 6. Reported a bug (FB8591101). To me this seems to be a regression as separate modules should be allowed to contain same type names in Swift and this worked in previous Xcode versions.
1
LucasA. OP
Aug ’20
Following this ticket, since I have the same problem and I can't figure it out.



1
kennyevo OP
Sep ’20
Following this, this bugs me since the first xcode12 beta, it was working fine in xcode11.
1
kickerbm0821 OP
Sep ’20
Following this, I'm still having this issue with XCode 12.0 Beta 6. Is there any official response from Apple regarding this? If it's deemed as an expected behaviour in the future, we need to plan a big code update...
0
ztcz OP
Sep ’20
Is there anything new regarding this?
I have this issue with Alamofire and Kingfisher.
0
kennyevo OP
Sep ’20
Still having this issue with XCode12 GM
0
Carlos EigenSpace OP
Sep ’20
I can confirm that this is still happening on Xcode 12 GM seed.
0
ionini OP
Sep ’20
Issue is still present on the released non-beta Xcode 12.
1
draupnir OP
Sep ’20
Same here.
I had to force rename one of third-party class name...
0
shlesberg OP
Sep ’20
Same here. The only workaround I've found is to rename one of the realisations
0
matiasem OP
Sep ’20
Hi! I had the same issue. I solve it by doing this:

  1. Close Xcode

  2. On command line write pod deintegrate and then pod install

  3. Open Xcode and problem should be solved.

Sorry for my english :p
Hope it helps!
0
semyen.ignatov OP
Sep ’20
The issue reproduces in Xcode 12.2 beta 2 (12B5018i).
0
mennya OP
Sep ’20
Following this ticket, since I have the same problem and I can't figure it out.
this happens only in new build system when use legacy its not happen
0
kamokaizen OP
Sep ’20
Same exception for me and project could not be compiled.

XCode 12 conflicted frameworks;

  • HGPlaceholders

  • Material

'CollectionView' has different definitions in different modules; first difference is definition in module 'HGPlaceholders.Swift' found property name 'collectionViewLayout'
0
Xcode 12 different definitions in different modules build error
First post date Last post date
 
 
Q