Swift Playgrounds Author Template for Xcode 11.3 cannot be built because of PlaygroundSupport.framework issues
Originator: | igorferreiracastanheda | ||
Number: | rdar://FB7587518 | Date Originated: | 18/02/2020 |
Status: | Open | Resolved: | |
Product: | Developer Tools/Swift Playgrounds | Product Version: | Xcode 11.3.1 |
Classification: | Incorrect/Unexpected Behavior | Reproducible: | 100% |
The latest "Swift Playgrounds Author Template for Xcode 11.3" available on developer resources, cannot be built with Xcode 11.3. This is true because the "PlaygroundSupport.framework", and "PlaygroundBluetooth.framework" provided with the sample are built with Swift 5.1 and cannot be imported to Swift 5.1.3 Please list the steps you took to reproduce the issue: - Download the resource at https://download.developer.apple.com/Developer_Tools/Swift_Playgrounds_Author_Template_for_Xcode_11.3/Swift_Playgrounds_Author_Template_for_Xcode_11.3.xip - Extract the content of the XIP - Open Template/PlaygroundBook.xcodeproj on Xcode 11.3 - Try to run either "PlaygroundBook" scheme, or "LiveViewTestApp" scheme What did you expect to happen? The project should be able to build, and show the content of the Playgrounds Book What actually happened? The project fails to build with the error: "[...]/Swift_Playgrounds_Author_Template_for_Xcode_11.3/Template/PlaygroundBook/Modules/BookCore.playgroundmodule/Sources/LiveViewSupport.swift:9:8: error: module compiled with Swift 5.1 cannot be imported by the Swift 5.1.3 compiler: [...]/Swift_Playgrounds_Author_Template_for_Xcode_11.3/Template/SupportingContent/PlaygroundsFrameworks/maccatalyst/PlaygroundSupport.framework/Modules/PlaygroundSupport.swiftmodule/x86_64-apple-ios-macabi.swiftmodule" Configuration: Xcode Version 11.3.1 (11C504) macOS Version 10.15.3 (19D76)
Comments
Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!