We are aware of an issue with our current Xamarin.iOS build that may prevent submission of watchOS 1 apps built using WatchKit. We are working on a hotfix for this issue, and hope to have updated builds for both Xamarin Studio and Visual Studio out later this week.
In the interim, we are making available a preview build of an updated Xamarin.iOS that is compatible with the current Xamarin Studio stable build that should address this issue. This preview is not compatible with Xamarin.VS, but the upcoming Stable hotfix should address this for everyone, including VS users.
[Xamarin.VS / Xamarin.iOS] – watchOS 1 apps built with WatchKit will be rejected during submission with the notification “Invalid WatchKit Support”.
** UPDATE – This build now also includes a fix for HTTPClient Authentication not working correctly. The additional should also be included in Cycle 5 Service Release 3 when it goes to Stable. **
We are aware of an issue hitting iOS developers right now that we are addressing, but won’t officially be released until Cycle 5 Service Release 3 goes to Stable (likely early August). However, for those of you who need to submit Watch Apps right now and are blocked, there is a workaround that can be used, or you can try out the updated hotfix build below, which is based off the current Stable (but has not been tested by our internal QA).
Rather than delay Service Release 3 to test this specific build, we’re simply providing it for download as a temporary measure. We will be including this same patch in our Service Release 3 build as well, where QA will be testing it as part of the standard process before releasing to Stable.
- [Xamarin.VS] – The above mentioned workaround for Watch App submission will not work for VS, so the below build must be used to successfully submit to the App Store.
- Xamarin.iOS 188.8.131.52 [Download]
- Issues Addressed:
- 30958 – Fixes an issue with incorrect Watch App Info.plist UIDeviceFamily array preventing Watch App submission.
- 30869 – Fixed an issue with HTTPClient Authentication not working correctly.
We are releasing an updated set of builds to the Stable channel in order to address the issues noted in our iOS9/El Capitan Technical Preview blog post. As noted in that post, we feel we’ve completed sufficient testing on the Xamarin.iOS SDK that resolves the issues affecting both 32 and 64 bit apps running on iOS 9. With this new Xamarin.iOS release, you should be able to rebuild and re-submit your apps using Xcode 6 and have them run against iOS 9 previews, ready to prepare them for the fall release of iOS 9. Head over to our developer page to read up on prepping your app for iOS 9.
We will also be posting previews of the Xamarin.iOS SDK that supports Xcode 7 and the iOS 9 APIs soon. Those builds will be distributed via a preview site, and we will have a new blog post up when they are available.
- [Xamarin.VS] – Debugging on iOS 9 devices from Visual Studio is not yet supported.
Yesterday Apple released the first previews of both iOS 9 and OS X El Capitan. We are working full-speed to add support for both iOS 9 and El Capitan right now, and we’ll keep you posted as things progress.
For iOS 9, we are investigating an issue that is causing a number of Xamarin apps to crash on startup. As we’re digging into this, the issue seems to be specific to apps that include 32-bit support.
Apple made some dramatic changes to OS X by making /usr/bin read-only, even with root access, so we’re working on making support for Xamarin Studio and the Xamarin Installer available as soon as possible to get up and running on OS X El Capitan.
As always, these are preview builds and we recommend staying with the stable releases of Xamarin and OS X and iOS until we make full support available for these previews available via this release blog and their preview sites.
Update: We have identified two issues that will affect both 32-bit and 64-bit apps on iOS 9. This has been released as a hotfix which you can find more detail on our hotfix blog post.