User Profile

Similar issue with the same error message for me. From a first library named "MyViews", I need to access a resource that is in a second library named "MyResources". If I run my app, it is working but the Xcode Preview produces this error: build aborted due to an internal error: planningFailed("multiple configured targets of \'MyResources\' are being created for iOS Simulator") SchemeBuildError: Failed to build the scheme "ResourcesInAnotherModule" unexpected service error: build aborted due to an internal error: planningFailed("multiple configured targets of \'MyResources\' are being created for iOS Simulator") Build system information: error: unexpected service error: build aborted due to an internal error: planningFailed("multiple configured targets of \'MyResources\' are being created for iOS Simulator") My package is: // swift-tools-version:5.3 // The swift-tools-version declares the minimum version of Swift required to build this package. import PackageDescription let package = Package(     name: "MyPackage",     platforms: [SupportedPlatform.iOS(.v14)],     products: [         .library(             name: "MyViews",             targets: ["MyViews"]),         .library(             name: "MyResources",             targets: ["MyResources"]),     ],     targets: [         .target(             name: "MyViews",             dependencies: ["MyResources"]),         .target(             name: "MyResources",             dependencies: []),     ] ) I have open a bug in Apple's Feedback Assistant for that issue with my project sample, number FB8930185.

I am having the same question. It seems that we have to add it as an iOS app in App Store Connect but I am wondering which Bundle Identifier to use as we have three ids (3 targets): com.myCompany.myApp com.myCompany.myApp.watchkitapp com.myCompany.myApp.watchkitapp.watchkitextension

Same issue for us.We did have a crash with a TestFlight build. The crash appeared in AppStore Connect's TestFlight crashes category but not in Xcode Organizer.New bug #FB7664572 created in Feedback Assistant

I have the same issue on watchOS 5.2 (just after installing the app).Radar #51025241 submitted (with a code sample and a workaround).My workaround is to call startAnimating on the next main loop like this:final class AnimationTableRowController: NSObject { @IBOutlet weak private var animatedImage: WKInterfaceImage? let isWorkaroundEnabled = false override init() { super.init() if isWorkaroundEnabled { // Note: Animation didn't start so we postpone the start: DispatchQueue.main.async { if let animatedImage = self.animatedImage { animatedImage.startAnimating() } } } } }