Apple today released the second beta of both watchOS 4.3.1 and tvOS 11.4 to developers. Both betas come two weeks after the respective releases of their first beta release.
watchOS 4.3.1 Beta 2
Apple does not provide detailed information as to what is contained in watchOS beta updates such as this, so what we know is limited to what users have discovered.
We do know that the first beta of watchOS 4.3.1 included an alert that appeared when an app built on the original watchOS 1 SDK is launched, warning the app may not be compatible with future versions of watchOS. This suggests the Cupertino firm will be dropping support for such apps sometime in the near future, much as it did for 32-bit apps in iOS 11.
Users with the proper configuration profiles installed on their device can install watchOS 4.3.1 beta 2 by loading the “Watch” app on their linked iPhone, and going to “General” -> “Software Update.” The Apple Watch will need to have at least 50% battery charge remaining, and it will need to be connected to its charger and be in range of the linked iPhone.
tvOS 11.4 Beta 2
The tvOS 11.4 Beta 2 release is for fourth and fifth-generation Apple TV models, and can be installed on devices via a profile that’s installed using Xcode.
tvOS 11.4 works in conjunction with iOS devices running iOS 11.4 to offer AirPlay 2 features such as the ability to play the same audio on multiple devices (including the Apple TV) throughout your home. Apple TV units running the tvOS 11.4 beta will once agains show up in the Home app.
Notes and Known Issues
Foundation
Known Issues
- Clients of NSURLSessionStreamTask that use a non-secure connection fail to connect when an error occurs during PAC file evaluation and the system is configured for either Web Proxy Auto Discovery (WPAD) or Proxy Automatic Configuration (PAC). A PAC evaluation failure can occur when the PAC file contains invalid JavaScript or the HTTP host serving the PAC file is unreachable. (33609198)
Workaround: Use startSecureConnection to establish a secure connection.
Mobile Device Management
Resolved Issues
- It’s not possible to skip all initial setup screens when using an MDM server configuration with Device Enrollment Program supervised devices. (36848833)
- Setup crashes when ‘auto-advance’ is enabled in DEP profile. (38621837)
