UPDATED – Xamarin.iOS Hotfix for Watch App Submission Technical Bulletin

** 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.

Known Issues 

  • [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. 

Products Released

  • Xamarin.iOS [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.