David Hanak Apparently, Apple's developers aren't messing around. On Monday, we had the arrival of the third beta of the upcoming operating systems iOS 11.1, watchOS 4.1 or tvOS 11.1, and today we have another version. It's been about an hour since Apple released the fourth developer version, but this time only for iOS and watchOS. A version for tvOS could arrive later.
It could be interest you
Dan Pražák As always, so soon after the release, it is not clear what new Apple has prepared for this release. It can be expected that some bugs will be fixed and some functionality will be added. We'll let you know as soon as information about what's new in this fourth beta hits the web. If you have a developer account and a current beta profile installed, you can download the fourth beta using the classic OTA method. You can see the official changelog (in English) below.
Notes and Known Issues
Arkite
Known Issues
- ContinuingfromabreakpointwhiledebugginganARSessionmayresultinVIObreaking. Any visual objects placed in the world/anchor are not visible. (31561202)
Audio
Resolved Issues
- Fixed an occasionally occurring issue with audio latency or distortion on iPad Pro (12.9-inch) (2nd generation) and iPad Pro (10.5-inch). (33844393)
AVFoundation
Resolved Issues
- Still capture requests using the 720p30 video format with the depthDataDeliveryEnabled property of AVCapturePhotoSettings set to true now works correctly. (32060882)
- Depthvaluesinthenondefault160x120and160x90depthdataformatsnowreturnthecorrectvalues. (32363942)
Known Issues
- When using the TrueDepth front-facing camera on iPhone X, setting the capture device's activeFormat to a binned video format (see AVCaptureDeviceFormat isVideoBinned) for capture and enabling delivery of camera calibration data causes the resulting AVCameraCalibrationData to contain invalid information for the intrinsicMatrix property. (34200225)
- Workaround: Select an alternate capture format whose isVideoBinned property is false.
- Note: Configuring a capture session using a session preset never selects binned formats.
Certificates
Resolved Issues
- Client certificate-based authentication now works for servers using TLS 1.0 and 1.1. (33948230)
EventKit
Known Issues
- Initializing an EKCalendarChooser from EventKit can result in an app crash. (34608102)
- Storing data to a nondefault event store in EventKit may not work. (31335830)
FileProvider
Resolved Issues
- Apps with a deployment target earlier than iOS 11 that subclass NSFileProviderExtension now work on versions of iOS prior to iOS 11. (34176623)
Foundation
Resolved Issues
- NSURLSession and NSURLConnection now load URLs correctly when the system is configured with certain PAC files. (32883776) 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.
Location Services
Resolved Issues
- Data from an external GPS accessory is now accurately reported. (34324743)
Notifications
Resolved Issues
- Silent push notifications are processed more frequently. (33278611)
ReplayKit
Known Issues
- For a broadcast extension that a user starts from within an app, the value for the RPVideoSampleOrientationKey of the CMSampleBufferRef of type RPSampleBufferType is always portrait. Starting the broadcast extension from the Control Center returns the correct value. (34559925)
Safari
Resolved Issues
- Loading of webmail clients now behaves correctly. (34826998)
Vision
Known Issues
- VNFaceLandmarkRegion2D is currently unavailable in Swift. (33191123)
- Facial landmarks identified by the Vision framework may flicker in temporal use cases such as video. (32406440)
W
Resolved Issues
- JavaScript execution during WKNavigationDelegate policy decisions now works correctly. (34857459)
Xcode
Known Issues
-
Debugging a disabled Messages extension may cause the Messages app to crash. (33657938)
-
Workaround: Enable the extension before starting the debug session.
-
After a simulated iOS device starts up, it is not possible to pull down the Lock screen. (33274699)
-
Workaround: Lock and unlock the simulated device and then reopen the Home screen.
That Apple developers are not hanging around? Every year, a completely unfinished iOS is released with fundamental problems that are fixed at least ten times by Christmas. I would much prefer if the new iOS was tweaked once every two years! Same with macOS.
That Apple developers are not hanging around? Every year, a completely unfinished iOS is released with fundamental problems that are fixed at least ten times by Christmas. I would much prefer if the new iOS was tweaked once every two years! Same with macOS.
exactly !
The iOS 11.1 version is mainly because of iPhone X. It is finished on it because iPhone X will have iOS 11.1 by default
The iOS 11.1 version is mainly because of iPhone X. It is finished on it because iPhone X will have iOS 11.1 by default
There are hundreds of millions of iPhones in the world for which iOS 11 is intended. If it doesn't work on them, it's a big problem and the release of a new model (still with poor availability) doesn't justify it. If they can't make it in a year, don't publish it. Who would mind having a "new" iOS after a year or two?
Where did you come across that update? Now I've checked my phone and watch and still the latest update is 11.0.3 and on the watch 4.0.