قالب وردپرس درنا توس
Home / Tips and Tricks / Apple has just released the first public beta version for iOS 13.1 – News «iOS & iPhone :: Gadget Hacks

Apple has just released the first public beta version for iOS 13.1 – News «iOS & iPhone :: Gadget Hacks



Apple shocked us yesterday when it released Beta 1 for iOS 13.1 developers. This was an unprecedented move as iOS 13.0 is still in beta testing and Apple has never released a "point" beta before the stable base version. And now you can get iPhone 13.1 for iPhone when you're in public beta.

The release of public beta is not a complete surprise. When public beta was discontinued on the same day as the developer beta release, it was only a matter of time before Apple introduced the public beta version. However, as in the past, Apple could have waited longer for this release.

From now on, the public beta 1 for iOS 13.1 will be the developer version of Beta 1

(public beta for iOS 13.0 was named one) lower than its developer-version counterpart). And the update seems to indicate that Apple has completed the beta test for iOS 13. Public beta 7 may be the "gold master" for the iOS 13 release we will receive next month.

Beta 8 for developers is still available So it's possible we'll see Beta 9 and Dev's public beta 8 before releasing iOS 13. Since the public beta now runs on iOS 13.1, it is likely that new beta versions for iOS 13.0, if any, will be for developers only because you will not be able to choose between the latest versions of iOS 13.0 or 13.1. There is also a slim chance that iOS 13.1 will be the first stable release released in September. In this case, it would be a first for Apple.

The first public beta for iOS 13.1 is not without the numerous new features and changes. Shortcut Automation has returned, as well as ETA in Maps and AirPod Audio Sharing. These three iOS 13 features have been removed in previous betas. Apple has also fixed errors in the Notes app, so the app will not deliver any unexpected results. If you rotate the device in landscape mode after selecting colored lines with the Lasso tool, these colors will be preserved instead of black in color.

Also, HEVC video is supported with alpha channels. This means that in iOS 13.1 you can capture videos with an invisible or transparent background, which is essential for editing green screens. VentureBeat announces that this feature may be available after Apple's recent purchase of the Spektral app, which allows live editing of backgrounds.

When you turn on the Share sheet in iOS 13.1, your fast options will be hidden in both light and dark modes. A reboot does not fix the problem. On a positive note, AirDrop now includes product icons, a new change to the Share sheet. All iPhone models now also seem to have dynamic black wallpapers, a feature once reserved only for OLED displays.

Read the following Release Notes for 13.1 dev Beta 1 (same as Public Beta 1):

iOS & iPadOS 13.1 Beta Release Notes:

Overview

The SDK for iOS and iPadOS 13 supports development of apps for iPhone, iPad and iPod touch devices with iOS and iPadOS 13. The SDK is included Included with Xcode 11 Beta, available at Beta Software Downloads. For Xcode 11 compatibility requirements, see the release notes for Xcode 11 Beta 5.

Developers using iOS 13 Beta 6 must also upgrade to Xcode 11 Beta 5.

Warning

If your watch is running watchOS 6 beta, you must upgrade to watchOS 6 beta 2 or later before upgrading to iOS 13 beta 6. Otherwise, your watch will stop connecting to your phone. (52854192)

General – Known Issues

  • Snapshots for apps that use Metal may appear unexpectedly in the App Switcher. (53121694)

General – Obsolete

  • The UIApplicationExitsOnSuspend key is no longer supported in iOS and iPadOS 13. Update your apps to handle modern multitasking. (43958234)

Audio – New Features

  • Voice processing mode can now be enabled in AVAudioEngine. (50906329)
  • The new AVAudioNode types can be used to wrap a custom block to send or receive data in real time.
  • For an AVAudioEngine-based app, there's a new way to get a list of all attached nodes available to an AVAudioEngine instance.
  • A new rendering mode in AVAudioEnvironmentNode automatically selects the best spatial audio rendering algorithm based on the output device.
  • A new AVAudioSession property lets you play system sounds and haptics while the session is actively using audio input.
  • A new listing, AVAudioSession.PromptStyle, informs apps about what type of voice prompts they should play based on other audio activity in the system.
  • With AVAudioSession.RouteSharingPolicy, apps can now set route sharing policies for audio and video to routes to the same location as AirPlay.
  • Audio Unit extensions now support user preferences that are available to all host applications.

Audio Obsolete

  • The OpenAL framework is outdated and still exists for compatibility. Transition to AVAudioEngine for spatial audio features.
  • AUGraph is no longer used in favor of AVAudioEngine.
  • Inter-app audio is no longer supported. Use Audio Units for this feature in the future.
  • Carbon Component-based Audio Units are outdated and will no longer be supported in a future release.
  • Legacy Core Audio HAL audio hardware plug-ins are no longer supported. Use audio server plug-ins for audio drivers in the future.

Audio Sharing – New Features

  • Audio sharing is compatible with AirPods (1st generation or later) and PowerBeats Pro. iPhone 8 or later, iPad Pro 12.9-inch (2nd generation or later), iPad Pro 11-inch, iPad Pro 10.5-inch, iPad (5th generation or later), iPad Air (3rd generation), iPad mini (5th generation), or iPod touch (7th generation or later) is required. (51331268)

AVFoundation – New Features

  • AVFoundation now supports encoding video with alpha channels using HEVC. Videos encoded in this way are widely supported in AVFoundation APIs and Safari on Web pages. Technical details about the format can be found in the specification of the interoperability profile. (8045917)

Core Haptics Known Issues

  • By default, haptics are disabled when microphone capture begins. You can override this by setting the AVAudioSession property allowHapticsAndSystemSoundsDuringRecording to true before enabling the audio session. (25811898)
  • Events such as audioContinuous, hapticContinuous, and audioCustom can not continue during the event. There is no output for this event, only for subsequent events. This applies to playback at a specific time offset as well as for searching and resuming. (29274583)
  • CHHapticDynamicParameter non-zero relative time instances sent as part of a sendParameters (_: atTime 🙂 call to a CHHapticAdvancedPatternPlayer with the atTime parameter set to 0.0 are not applied correctly at the beginning of CHHapticPatterns relative time not equal to zero. This does not occur with a CHHapticPatternPlayer. (46316890)
  • Both vibrations generated by AudioServicesPlaySystemSound (_ 🙂 and vibration patterns generated by the user-created vibration tip user interface are muted compared to earlier versions of iOS. (47448156)
  • Parameter curves are not supported on a CHHapticAdvancedPatternPlayer, only with a CHHapticPatternPlayer. No error is generated when passing a CHHapticPattern with a parameter curve to a CHHapticAdvancedPatternPlayer. (47891515)
  • When starting an app for the playback category, for example, B. Music, in the background occurs a short audio distortion. For example, a brief distortion occurs when you launch the app from the Control Center while Core Haptics audio playback is already running using a "playAndRecord" audio session. (48121467)
  • After decompression into uncompressed floating-point samples, the total limit for all AudioCustom resources per process is eight megabytes. (48659023)
  • Multiple overlapping parameter curves for the same CHHapticDynamicParameter.ID may result in rendering artifacts. (50026384)
  • The maximum duration for a haptic-continuous haptic event is 30 seconds. Events that exceed this limit can be created and accepted by the CHHapticPatternPlayer. However, haptic playback disappears after 30 seconds. (51322525)

Core Image – New Features

  • The initializers init (imageURL: options 🙂 and init (imageData: options 🙂 do not support RAW version 5 and earlier. Version 6 and higher are still supported. (50911303)
  • New APIs have been added to instantiate and modify the built-in core image filters.
  • The CICoreMLModel filter has been enhanced to support models with an input or output of type MLFeatureType.multiArray.
  • Support for Metal CIKernel instances Arguments with arbitrarily structured data.
  • Metal CIKernel instances support the return of a group of 2 × 2 pixels.
  • The integer values ​​of CIFormat symbols, such as For example, ARGB8 has been changed to a new set of values ​​that are cross-platform consistent. The previous values ​​are still supported for backward compatibility. However, you should avoid dependencies on specific numeric values.

Finding Known Issues

  • When you perform an action in "Find My Friends" that generates an email, you may see references to the "Find My Friends" and "Find My iPhone" apps. (51123613)
  • While iOS and iPadOS 13 are still in beta, offline searches are limited.

Resolved Issues

  • The state and activity functions continue to work if you set the period length to be longer than the cycle length in the cycle trace options. (54313089)

iCloud Known Issues

  • After upgrading to iOS 13 Beta 6, iCloud Drive may be synced over an extended period of time. If you notice missing files, you can find them in a "Restored Files" folder under "On my iPhone / iPad" in the Files app. (53772753)
  • When creating a new page, number, or keynote document in a shared folder, the following message may be displayed: "Unable to connect to iCloud." (50827963) Workaround: Close the document and reopen it.

Mail – New Features

  • Ignore Blocked Senders can now be enabled under Settings> Mail. The list of blocked contacts is shared with News, FaceTime, and Phone. (50775961)

Network – What's New

  • For better security, URLSession no longer determines the MIME type when the server sends content type application / octet-stream. (7820658)
  • The NSURLRequest.CachePolicy.reloadRevalidatingCacheData and NSURLRequest.CachePolicy.reloadIgnoringLocalAndRemoteCacheData APIs are now available. (49660334)
  • Effective in iOS 13 Beta 4, the copy attribute of the httpBodyStream property of NSMutableURLRequest is enforced. If the main part data is mutated after calling the property setter, the data sent in the HTTP request will not include that mutation. Calling the property getter no longer returns an NSMutableData reference, even if the setter was called with data of that type. As of iOS 13 Beta 5, apps built with the iOS 12 SDK or earlier SDKs use legacy behavior. (53427882)
  • The CNCopyCurrentNetworkInfo API has been changed to protect privacy. For more information, see the updated API documentation and the headers. (52707167)
  • All URLSessionTask instances with a GET HTTP method that contain a body now generate the error NSURLErrorDataLengthExceedsMaximum. (46025234)

Network – Resolved Issues

  • The delegate callback for urlSession (_: taskIsWaitingForConnectivity 🙂 now works as expected. (54309264)

Network – Obsolete

  • Support for FTP and file URL schemes for automatic proxy configuration (PAC) has been removed. HTTP and HTTPS are the only supported URL schemes for PAC. This applies to all PAC configurations, including, but not limited to, configurations set using settings, system settings, profiles, and URLSession APIs such as connectionProxyDictionary and CFNetworkExecuteProxyAutoConfigurationURL (_: _: _: _ :). (28578280)
  • The URLSession and NSURLConnection APIs no longer support SPDY. Servers should use HTTP 2 or HTTP 1.1. (43391641)

Notes – resolved issues

  • Using search in notes no longer produces unexpected results. (48238242)
  • When you use the Lasso tool to select colored character strokes and then rotate your device into landscape mode, the strokes are no longer converted to black. (54246012)

PencilKit – Resolved Issues

  • If your PencilKit app is linked and the deployment target is iOS 13.1 or higher, you can now submit it to the App Store. (53811027)

RealityKit Known Issues

  • The camera feed remains visible at the base of objects loaded from a reality file when ARView.Environment.Background is on ARView.Environment.Background.skybox (_ 🙂 is set. (53715030) – Workaround: Disable Ground Shadows when setting the background to ARView.Environment.Background.skybox (_ 🙂 by setting ARView.RenderOptions to disableGroundingShadows.

RealityKit – Resolved Issues

  • Reality files with object anchors are now anchored to AR Quick Look and in applications to those objects. (53689364)

Screen Time – Known Issues

  • When you enable device sharing, the screen time settings are not synchronized with iCloud until you restart your iOS device. Any changes you make to the screen time settings on this device before reboot will be lost. (50194586)

Siri Known Issues

  • The supportedOnDeviceRecognition property always returns false on first access. If you access it again after a few seconds, the correct value is returned. (47822242)
  • Shortcuts opened on iOS and iPadOS 13 Beta are automatically updated and can no longer be opened on iOS 12. When an iOS 12 device and an iOS 13 device share an iCloud account, shortcuts can no longer be used on the device running iOS 12. (50873839) Workaround: Disable iCloud sync between Devices with iOS and iPadOS 13 Beta and devices with iOS 12.
  • Currently INSearchForMediaIntent is the only supported answer for INSearchForMediaIntentResponseCode.continueInApp. (51010311)

Siri Bug Fixes

  • Join automations are now available. (53182885)

SwiftUI – New Features

  • You can now create a color from a UIColor or NSColor. (49833933)
  • NSManagedObject now corresponds to ObservableObject. The new @FetchRequestproperty wrapper can control views from the results of a fetch request, and managedObjectContext is now included in the environment. (50280673)
  • gesture modifiers are renamed for consistency. For example, tapAction (count: _ 🙂 is renamed onTapGesture (count: perform :), and longPressAction (minimumDuration: maximumDistance: _: pressing 🙂 is renamed onLongPressGesture (minimumDuration: maximumDistance: performing :). (50395282)
  • Text now has a default line limit of zero, wrapping it by default. (51147116)
  • ContentSizeCategory and several other enumerations are now case-sensitive. (51168712)
  • SegmentedControl is now a picker style. (51769046)
  • BindableObject is replaced by the ObservableObject protocol from the Combine framework. (50800624)

You can make a manual adjustment to ObservableObject by defining an objectWillChangePublisher that is output before the object changes. By default, however, ObservableObject automatically synthesizes objectWillChange and issues it before @PublishedProperties change.

// RoomStore.swift
import Foundation

class RoomStore: ObservableObject {
@Published var rooms: Room =
}

struct Space: Identifiable {
var ID: UUID
var Name: String
var Capacity: int
var hasVideo: Bool
}

// ContentView.swift
Import SwiftUI

struct ContentView: View {
@ ObservedObject var store: RoomStore

var body: some View {
NavigationView {
List (store.rooms) {room in
RoomCell (room: room)
}
.navigationBarTitle ( "Rooms")
}
}
}
@ObjectBinding is replaced with @ObservedObject.

  • The identifiable protocol is now part of the Swift standard library. As a result, your model files no longer need to import the SwiftUI framework. (SE-0261)
  • The EnvironmentValues ​​structure has four new properties for reading accessibility values ​​from the environment: accessibilityDifferentiateWithoutColor, accessibilityReduceTransparency, accessibilityReduceMotion, and accessibilityInvertColors. (51712481)
  • The modifier color (_ 🙂 for text is renamed to foregroundColor (_ 🙂 to ensure consistency with the more general view modifier foregroundColor (_ :). (50391847)
  • The BindableObject protocol request now reads willChange instead of didChange and should now be sent before the object changes, rather than after it has changed. This change allows improved merging of change messages. (51580731)
  • The RangeReplaceableCollection protocol has been extended by a remove method (atOffsets 🙂 and the MutableCollection protocol by a move method (fromOffsets: toOffset :). Each new method uses IndexSetinstances, which you use with the onMove (perform 🙂 and onDelete (perform 🙂 modifiers for ForEach views. (51991601)
  • Added improved display modifiers: table (isPresented: onDismiss: content :), action sheet (isPresented: content 🙂 and warning (isPresented: content 🙂 – along with isPresented in the environment – replace the existing presentation (_ :), Sheet, Modal, and PresentationLink types. (52075730)
  • The APIs for creating animations have been updated. The basic animations are now named after the curve type, eg. B. linear and easeInOut. The interpolation-based feather (mass: stiffness: damping: initial velocity 🙂 animation now interpolates Spring (mass: stiffness: damping: initial velocity 🙂 and FluidSpring (stiffness: damping fraction: mixture duration: time step: idle threshold 🙂 is now Spring (answer: dampingFraction: blendDuration 🙂 or interactiveSpring (reaction: dampingFraction: blendDuration :), depending on whether the animation is controlled interactively or not. (50280375)
  • An initializer for creating a font from a CTFont has been added. (51849885)
  • You can format a navigation view with two new style properties: StackNavigationViewStyle and DoubleColumnNavigationViewStyle. By default, navigation views on the iPhone and Apple TV visually mirror a navigation stack, while a split-view navigation view is displayed on the iPad and Mac. (51636729)

If you use the DoubleColumnNavigationViewStyle style, you can provide two views when creating a navigation view – the first is the master and the second is the detail. Example:

NavigationView {
MyMasterView ()
MyDetailView ()
}
.navigationViewStyle (DoubleColumnNavigationViewStyle ())

SwiftUI – Resolved Issues [19459004InstancesUseSizeSizeInformationAssetCatalogsAreConfigured(49114577)

SwiftUI – Deprecated

  • Older SwiftUI APIs have been removed from previous versions of iOS 13 Beta. (53310683)
  • NavigationDestinationLink and DynamicNavigationDestinationLink are deprecated. Its functionality is now included in NavigationLink. (50630794)
  • The type length is replaced by CGFloat. (50654095)
  • TabbedView is now called TabView. (51012120)
  • HAlignment and VAlignment are now obsolete. Instead, use the more flexible HorizontalAlignment or VerticalAlignment types and use TextAlignment for text. (51190531)
  • The SelectionManager log has been removed. Use the instances Optional and Set directly for the selection. (51557694)
  • The environment value isPresented is deprecated and is replaced by the more general representationMode. (51641238)
  • The StaticMember log is out of date. Instead, use directly protocol-compliant types. For example, use an instance of WheelPickerStyle directly instead of the static wheel element. (52911961)
  • Complex overloads on the background (_: alignment 🙂 and border (_: width 🙂 modifiers are deprecated. Use shapes in a background (_: alignment 🙂 or overlay (_: alignment 🙂 to draw them instead. (53067530)
  • SwiftUI APIs that were obsolete in previous betas have been removed. (52587863)
  • The identified (by 🙂 method in the collection log is no longer recommended in favor of the dedicated initializers init (_: id: selection: rowContent 🙂 and init (_: id: content :). (52976883, 52029393)

The retrospective compliance of Int with the identifiable protocol has been removed. Modify any code that relies on this conformance to pass itself to the id parameter of the corresponding initializer. Constant ranges of Int are still accepted:

List (0 .. <5) {
Text ("spaces")
}

However, you should not pass an area that changes at run time. If you use a variable that changes at run time to define the range, views in the list will be displayed according to the original range and any subsequent updates to the range will be ignored.

  • Various extensions to the binding structure are removed. (51624798)

If you have the following code:
struct LandmarkList: View {
var landmark: Landmark
@Binding var favorites: Set

var body: some View {
List (Landmarks) {Landmark in
Toggle (landmark.name, isOn: self. $ Favorites.contains (landmarkID))
}
}
}

Define the following index for the set structure:
extension set {
index (member: element) -> bool {
get {contains (member)}
set {
if newvalue {
insert ( member)
} else {
remove (member)
}
}
}
} Then change self. $ favorites.contains (landmarkID) in self. $ favoritelandmarkID.

  • The conditional compliance of the binding structure with the collection log has been removed. (51624798)

If you have the following code:
struct LandmarkList: View {
@Binding var landmark: Landmark

var body: some View {
List (landmarks) {landmark in
Toggle (marker.value.name, isOn: landmark .isFavorite)
}
}
}
Define the following collection type:
struct IndexedCollection : RandomAccessCollection {
typealias Index = Base.Index
typealias Element = (Index: Index, Element: Base.Element)

let base: Base

var startIndex: Index {base.startIndex}

var endIndex: Index {base.startIndex}

Function index (after i: index) -> index {
base.index (after i)
}

Function index (before i: index) -> index {
base.index (before: i)
}

Function index (_ i: index, OffsetBy distance: int) -> index {
base.index (i, OffsetBy: distance)
} [19659002] Index (Position: Index) -> Element {
(Index: Position, Element: Base Position)
}
}

Extension RandomAccessCollection {
func indexed () -> IndexedCollection {
IndexedCollection (base: self)
]}
} Then update your code to:
struct LandmarkList: View {
@Binding var landmarks: Landmark

var body: some View {
List (landmarks.indexed (), id: .1.id) {(index, landmark) in
Toggle (landmark name, isOn: self. $ landmarksindex.isFavorite)
}
}
}

  • The relativeWidth (_ :), relativeHeight (_ 🙂 and relativeSize (width: height 🙂 are deprecated. Instead, use other modifiers, such as frame (minWidth: idealWidth: maxWidth: minHeight: idealHeight: maxHeight: alignment :). (51494692)

Third-party apps – Known issues

  • You may not be able to stream to a Chromecast device. (51334673)

UIKit – New Features

  • The UITableViewCell class no longer changes the backgroundColor or isOpaque properties of the content view and its subviews when cells are highlighted or selected. Setting an opaque background color for subviews of the cell inside (and including) the content view may affect the appearance when the cell is highlighted or selected. The easiest way to fix problems with your subviews is to make sure the backgroundColor is set to zero or clear and the opacity is wrong. However, if necessary, you can override the setHighlighted (_: animated 🙂 and setSelected (_: animated 🙂 methods to manually change these properties in your subviews when you move to or from the highlighted and selected states. (13955336)
  • Since iOS 8, to use UISearchController with UINavigationController, the controller's definePresentationContext property must be set to true for the top view. Otherwise, you may experience subtle errors that are difficult to detect and correct. As of iOS and iPadOS 13 Beta, UINavigationController automatically sets the viewPropertyControl's definePresentationContext property to true if the navigationItem of a view controller contains a non-nilsearchController when the view controller is displayed in a navigation controller. If you are targeting earlier versions of iOS, set this property before your search controller becomes active. (31338934)
  • The UIRefreshControl class no longer changes the contentInset of its scrolling view directly. Instead, the Content Inset adjustments are reflected in the adjusted scrolling content set. The only exception is that the contentInsetAdjustmentBehavior of the scrolling view is set to UIScrollView.ContentInsetAdjustmentBehavior.never. In this case, the UIRefreshControl instance changes the contentInset directly as in previous versions. (35866834)
  • When you implement cells with automatic resizing in a UITableView by overriding sizeThatFits (_ 🙂 without using the automatic layout, the returned height is interpreted as the desired height for the content view of the cell, and UITableViewCell Automatically adds all extra height required to leave room for the cell separator. Wenn Sie die manuelle Größenanpassung auf diese Weise implementieren, ist die contentView-Breite der Zelle garantiert genau, damit Sie sie bei manuellen Layoutberechnungen verwenden können, wenn sizeThatFits (_ 🙂 für die UITableViewCell aufgerufen wird. (39742612)
  • In Merkmalumgebungen, wie z. B. Ansichten und Ansichtscontroller, wird die Eigenschaft traitCollection jetzt während der Initialisierung mit Merkmalen gefüllt. Diese anfänglichen Merkmale stellen eine Vorhersage der endgültigen Merkmale dar, die die Merkmalumgebung erhält, wenn sie der Hierarchie hinzugefügt wird. Da es sich bei den Merkmalen, die während der Initialisierung ausgefüllt werden, nur um Vorhersagen handelt, können sie sich von den Merkmalen unterscheiden, die tatsächlich in der Hierarchie einmal empfangen werden. Warten Sie daher nach Möglichkeit mit der Ausführung von Arbeiten, die die traitCollection verwenden, bis die Ansicht oder die Ansicht des Ansichtscontrollers in die Hierarchie verschoben wurde. Das bedeutet, dass das Fenster einen Wert ungleich Null zurückgibt, sodass Sie keine Arbeit wegwerfen müssen erfolgt unter Verwendung der vorhergesagten Merkmale, wenn die tatsächlichen Merkmale unterschiedlich sind. Die Verwendung der traitCollection empfiehlt sich während des Layouts, z. B. innerhalb von layoutSubviews (), viewWillLayoutSubviews () oder viewDidLayoutSubviews ().
  • Die Methode traitCollectionDidChange (_ 🙂 wird nur aufgerufen, wenn sich der Wert eines Merkmals ändert. Wichtig ist, dass traitCollectionDidChange (_ 🙂 nicht aufgerufen wird, wenn die ursprünglichen vorhergesagten Merkmale den endgültigen Merkmalen in der Hierarchie entsprechen, da die Merkmalauflistung jetzt mit einer Vorhersage der endgültigen Merkmale in der Zielhierarchie initialisiert wird Die Hierarchie. Da es sich bei traitCollectionDidChange (_ 🙂 um einen Invalidierungsrückruf handelt, mit dem Sie benachrichtigt werden, dass sich eines oder mehrere Merkmale geändert haben, überprüfen Sie Ihre vorhandenen Implementierungen dieser Methode sowie die UIContentContainer-Methode willTransition (to: with :), um festzustellen, wo Sie möglicherweise sind Ich habe mich darauf verlassen, um die Ersteinrichtung auszulösen. Der beste Ort, um Arbeiten, die die traitCollection verwenden, faul auszuführen, ist eine der oben diskutierten layoutSubviews-Methoden. Denken Sie jedoch daran, dass diese Layoutmethoden jedes Mal aufgerufen werden, wenn Layout auftritt. (46818941)
  • Sie können jetzt die Debugprotokollierung aktivieren, um zu sehen, wann traitCollectionDidChange (_ 🙂 oder willTransition (to: with 🙂 für Ihre eigenen Klassen aufgerufen wird. Aktivieren Sie die Protokollierung mit dem folgenden Startargument: -UITraitCollectionChangeLoggingEnabled YES. Möglicherweise möchten Sie den Main Thread Checker vorübergehend deaktivieren, während Sie dieses Startargument verwenden und Ihre App über Xcode ausführen, um zusätzliche Protokollnachrichten für nicht verwandte Klassen zu vermeiden. (47858564)
  • Die contentView -Eigenschaft der UITableViewCell-Klasse wird immer randlos mit angrenzendem Zubehör sowohl an der vorderen als auch an der hinteren Seite angeordnet. Dadurch wird der Layoutcode optimiert, sodass Entwickler, die den richtigen Standardversatz wünschen, ihren Inhalt nicht mehr am Rand der Inhaltsansicht oder am Layoutrand ausrichten müssen, je nachdem, ob sich auf der nachfolgenden Seite ein Zubehör befindet oder nicht. Sie sollten ihren Code jetzt immer an den Layouträndern der Inhaltsansicht der Zelle auslegen, um die Standardsystemeinfügungen zu erhalten. Diese Einsätze werden basierend auf dem in der Zelle sichtbaren Zubehör automatisch an den Standardabstand des Systems angepasst. (48214114)
  • Sie können jetzt einen benutzerdefinierten Initialisierer aus einem Erstellungsblock aufrufen, der über instantiateInitialViewController (creator 🙂 oder instantiateViewController (identifier: creator 🙂 übergeben wird. Auf diese Weise können Sie Ansichtscontroller mit zusätzlichen Kontexten und Argumenten initialisieren und diese über Interface Builder in einem Storyboard definieren. Ein benutzerdefinierter Controller-Initialisierer muss seine super.init (coder 🙂 -Methode aufrufen und das Coder-Argument, das er empfängt, über den Erstellungsblock übergeben. (48313869)

UIKit – Bekannte Probleme

  • Das Angeben von UIWindowScene.DestructionRequestOptions in Swift ist derzeit nicht verfügbar. (51036709)

Sprachanalyse – Bekannte Probleme

  • Die Sprachanalyse ist derzeit nur bei Verwendung der serverbasierten Spracherkennung verfügbar. (53604093)

Watch – Bekannte Probleme

  • Nach der Aktualisierung auf iOS 13 Beta verschwinden möglicherweise Komplikationen aus der Apple Watch, wenn auf Ihrer Uhr nicht watchOS 6 Beta ausgeführt wird. (50507942)

Xcode – Neue Funktionen

  • CAMetalLayer ist jetzt im Simulator verfügbar. (45101325)

Xcode – Behobene Probleme

  • Gespendete Verknüpfungen werden jetzt in der Suche angezeigt, während der Simulator verwendet wird. (50832782)
  • Changing the volume level in Simulator while a video is playing in Safari no longer mutes the audio. (51207286)

You can sign up through Apple&#39;s beta site, download and install the configuration profile, then update over the air. If you already have the profile, go to Settings –> General –> Software Update to begin the installation of the latest beta build, or you can wait until it installs automatically if "Automatic Updates" is enabled.


Source link