I transferred ownership of an iOS app that had an watch app included. The transfer went smoothly, however the App ID associated with the watch app: xxxxx watchkitapp did not get transferred to the new owner (neither did the watchkitapp.extension but I could delete this bundle ID myself).This prevents the new owner from distributing the app due to the conflict with the watchkit app bundle ID not being associated with the new developer. I could not delete the App ID for the watchkit bundle because the app was already on sale via the store.The bundle ID for the watch target can't be changed in the app, it gets an invalid binary error when trying to distribute a build to the AppStore.I went through the support process with apple who looked at deleting the ID, however I've been told this can't be done. Also that it can't be transferred by Apple themselves.So, warning to those who try a transfer for this type of app. You may well end up with an app that is "transferred" however updates cannot be distributed by the new owner.

I'm getting dynamic link errors (crashes) when running my app on pre SwiftUI 2 targets (in particular Mac OS 10.x) - error: dyld: lazy symbol binding failed: Symbol not found: _$s7SwiftUI15ScrollViewProxyVMa. (My app targets macOS 10.15 onward - SwiftUI 1+). I'm trying to use the new ScrollViewProxy (v2 to support automated scrolling of lists) and have this included in a class using the available attribute as per below: @available (macOS 11, *) final class ScrollingHelper {     private var proxy: ScrollViewProxy? I have conditionals elsewhere that only instantiate the class if running on v11. eg. If #available (macOS 11, *) to call a function with the header: @available (macOS 11, *), this called function uses the class. The app runs fine on v11. The linking error on pre v11 targets can be prevented if I simply comment out the declaration of the proxy in the ScrollingHelper class. I want a single version of the app that can be deployed to v10 or v11 targets with the new v11 feature used at runtime (on v11 targets), however this dynamic linking problem has me stuck. I hope I don't need to drop support for pre v11 :( Please help.