Was it entirely necessary to (in my opinion) unceremoniously break the library/framework solution that has been employed by 3rd party, iOS SDK developers for over a decade? I realize that XCFramework has been a topic of discussion since mid-2019 and a feature in Xcode 11 since fall-2019, but to effectively decommission a solution that has functioned well for many years (given the lack of integrated support for external SDK distribution in the Apple dev tools) in a "minor" Xcode release (i.e. functional in 11.3, broken in 11.4) seems rash.I recognize that the scripts and instructions provided to customers can be updated back into a functional state. I understand that when developer tools are updated a certain amount of risk is inherently accepted (which is why I do so infrequently and judiciously). Furthermore, I must admit excitement over an Apple-blessed solution to the SDK/framework distribution problem. However, my excitement is (which, technically, has now become "was") in regards to a potential, likely future when XCFramework adoption felt prudent and solid. For now, the present has been unceremoniously disrupted by perplexed customers that are using Xcode 11.4.