I'm having the same problem, updated to Xcode 9.3 (for other reasons I needed to have Xcode updated) and now I have the error "error HE0003: Could not load the framework 'DADocSetAccess'.
We are exploring ways to mitigate scenarios where users upgrade their SDKs before we ship our full support, and we hope to bring those to upcoming releases. That said, if you need to use Xcode 9.3 right away, or even on the very date of the release, you can always use the last available builds, the only downside is that they still have labels like "Preview" on them. The guidance that we have given our users historically is to hold off on upgrading your underlying tooling on the day of the launch until we ship the updates, this release was not the exception and we did post this guidance on March 29th:
The software has completed QA and is being published, and will be available this afternoon.
So I told the team to wait until this week to release. Releasing on the last few hours before a weekend is generally a bad idea, if anything goes wrong, it becomes very difficult to get any updates out.
This QA process takes about a day to complete, and would have pushed us to release the code on a weekend. You can find the support you need for Xcode 9.3 here:Īpple released 9.3 on Thursday, and while we could have released something right away, we wanted to run all of our tests against the official 9.3 to make sure we did not ship something broken. We have been publishing support for Xamarin to support Xcode 9.3 since the beta process started, so we have been tracking every change from Apple. It is a complete mess from my point of view. Issues like this one do happen to Xamarin maybe not regularly, but more often than expected, development itself is unnecessarily complex (more complex than with native approach, because you need to take care of the same things as when doing it natively plus the Xamarin part), tools are worse than those available for Java/Obj-C (Android Studio and AppCode) and unless you're doing something really simple, you need to code it twice, because there's no usable abstraction you could use for iOS and Android. Can't really see a good reason to use it. Overall, I'm hugely disappointed with Xamarin. They also didn't take any steps to warn their users. But still, Apple makes beta builds available long before they are made official, Xamarin had all the time they needed to prepare for this, but they didn't. I think people understand the risks and often the problem is simply caused by the autoupdate which is on by default.
They update without understanding the potential risks involved. It just amazes me that so many people might go 'oh there is a new XCode version out that I rely on to build iOS apps. It doesn't of course - but it certainly does feel like it when you've spent a working day trying to get your tools working again. It's almost a 'no effort' solution and would go a long way towards answering many complaints that "this sort of thing happens every time".
If Xamarin could maintain such a thing then every developer would know if it's OK to upgrade to each new version of iOS or Android (or other) SDKs and could largely avoid these issues. Nothing complicated - just a simple traffic light system. I'm advocating a simple status page shows their readiness with respect to the various SDKs available. In the absence of any clear guidance from Xamarin, why wouldn't they go for it? However, there are plenty of developers who aren't just rushing - they really do need to get code built with the latest SDK features. User7713 indeed experience shows it's a good idea to wait - particularly with Xamarin tools. Had Xamarin made it clear to everyone that there was an issue, and not to download Xcode 9.3, then this problem could have been avoided. We're often the ones who find out that things don't work well, which results in developer downtime. If we treated our customers in this way, we wouldn't have too many customers for too long.Īnd even if, for good technical reasons, the above is not possible, then Xamarin should make the position clear to their developers. I pay for an Enterprise version of the tools and I'm finding they are broken far too often. This has become the norm and it's not acceptable.
Even if there is a workaround (and please bear in mind that on previous occasions like this there has not been a good workaround) we should not have to be resorting to workarounds to keep our development tools working. One would have expected that Xamarin would make sure that their product is compatible before the Xcode publication, so that developers don't get stuck with broken tools. The beta for that solution has been available for quite some time. Whilst there might be some highly emotional language being used, it's not defensible to argue that Xamarin has only had a few days to make sure their product is compatible with the 9.3 Xcode.