[SR-11704] Swift 5.1.2 (Xcode 11.2) cannot import framework that have swiftinterface built on Swift 5.1 (Xcode 11.1)

[swift-ci]

Previous ID	SR-11704
Radar	rdar://problem/56923079
Original Reporter	taiki komaba (JIRA User)
Type	Bug

Environment

macOS 10.14.6

Xcode 11.1 (11A1027) and 11.2 (11B52)

Additional Detail from JIRA

Votes	0
Component/s	Compiler
Labels	Bug, LibraryEvolution
Assignee	None
Priority	Medium

md5: f1ed38a9dc02b014c38a882d29cd14c2

Issue Description:

I built framework with `BUILD_LIBRARY_FOR_DISTRIBUTION` parameter to support module stability on Swift 5.1.

But in Swift 5.1.2, cannot import that framework with below errors in swiftinterface file.

• Failed to load module 'Eureka'

• Unknown attribute '_staticInitializeObjCMetadata'

• Redundant conformance of 'AreaRow<Cell>' to protocol 'FormatterConformance'

Reproducible project

https://github.com/r-plus/modulestabilitytest

[beccadax]

@swift-ci create

[swift-ci]

Comment by Artem Loenko (JIRA)

We have the same issue, also related to UIKit subclasses, like:

@_staticInitializeObjCMetadata
final public class PhotoMessageCollectionViewCell : ChattoAdditions.BaseMessageCollectionViewCell<ChattoAdditions.PhotoBubbleView>
...

Reproducible by the same steps mentioned in the description for Chatto project.

P.S. Chatto is part of Swift Source Compatibility Suite and, usually, it helps us to catch problems in advance. Maybe this is a good idea to have a set of checks but for the module stability feature as well.

[swift-ci]

Comment by taiki komaba (JIRA)

still issued on Xcode 11.3 beta (11C24b)

[swift-ci]

Comment by kintan (JIRA)

still issued on Xcode 11.4
https://bugs.swift.org/secure/AddComment!default.jspa?id=23600

[swift-ci]

Comment by Artem Loenko (JIRA)

Can confirm. Still the problem on Xcode 11.4.

[swift-ci]

Comment by Tim Schmelter (JIRA)

I can confirm this is still a problem with Xcode 12.1, testing against binaries built in Xcode 11.4.1

[swift-ci]

Comment by Tim Schmelter (JIRA)

I have a barebones sample project that reproduces the issue. It includes pre-built binaries for easier testing, and is simpler relative to Chatto that dive (JIRA User) linked above, and self-contained unlike the sample project from the original bug posting.

Does anyone on the Swift team have insight into whether this issue is on anybody's radar for investigation?