قالب وردپرس درنا توس
Home / Tips and Tricks / Apple has just released iOS 13 Public Beta 7 for iPhone for software testers «iOS & iPhone :: Gadget Hacks

Apple has just released iOS 13 Public Beta 7 for iPhone for software testers «iOS & iPhone :: Gadget Hacks



Beta tests certainly have their advantages. You'll have to deal with bugs, but you'll be familiarized with new features before the general community. And when it comes to iPhones, there are over 200 new features in iOS 13 Beta. If you're already on board with iOS 13 Public Beta 6 for iPhone, you can upgrade this firmware as Apple has just released public beta 7.

The seventh public beta update comes just six days after the release of the public Beta Beta 6 and developer Beta 7. Apple indulges us with frequent beta updates. This is a welcome trend as previous beta versions of iOS 13 continued to diverge. New features and changes have been made in recent updates, including new e-mail blocking options, changing the Dark Appearance to Dark Mode, and restoring Folder Transparency to Normal.

By contrast, public beta 6 does not offer too many new features. In fact, we see some new errors in the release notes, and there's probably more.

Read the following release notes for iOS 1

3 public beta 7, which are identical for iOS 13 developers Beta 8.

iOS & iPadOS 13 Public Beta 7 Release Notes:

Overview

The SDK for iOS & iPadOS 13 supports the development of apps for iPhone, iPad, and iPod Touch devices with iOS and iPadOS 13. The SDK comes with the beta version of Xcode 11, which comes with the beta Software downloads is available. 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 it to watchOS 6 beta 2 or later before upgrading to iOS 13 beta 6. Otherwise, your watch can no longer connect to your phone. (52854192)

General – Known Issues

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

General – Deprecated

  • 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 allow you 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 prompt they should play based on other audio activity in the system.
  • AVAudioSession.RouteSharingPolicy now allows apps to 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 Release – 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 CHHapticPattern 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 automatic vibration user interface are dampened compared to previous versions of iOS. (47448156)
  • Parameter curves are not supported with 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, such as 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 for instantiating and modifying the built-in core image filters have been added.
  • 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 certain 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, the offline search feature is limited.

Troubleshooting Known Issues

  • Troubleshooting and activity functions no longer work if you set the period length to a longer value Cycle length in the cycle trace options. Make sure that your period length is set to a shorter duration than your cycle length. (54313089)

iCloud Known Issues

  • After upgrading to iOS 13 Beta 6, iCloud Drive may sync over a long 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.

iCloud Fixed Issues

  • The iCloud Drive section under Settings> General> iPhone Memory may not display the current status of the files on your device correctly. (50362095)

Localization – Resolved Issues

  • Devices set to use specific languages ​​no longer have a truncated or misaligned layout. (51068688)
  • Devices set to use specific languages ​​no longer display unlocalized text. (47765173, 51197936, 51270878)

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)

Music Known Issues

  • The status of the Sync Library option under Settings> Music may not reflect the current status of the feature on your device correctly. If you do not want to enable the feature, make sure that the switch is off. If your music library does not seem to be in sync with other devices, turn the switch off and then on again. (53957863)

Network New Features

  • For better security, URLSession no longer determines the MIME type when the server sends the application / octet-stream content type. (7820658)
  • The NSURLRequest.CachePolicy.reloadRevalidatingCacheData and NSURLRequest.CachePolicy.reloadIgnoringLocalAndRemoteCacheData APIs are now available. (49660334)
  • Starting with 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 Known Issues

  • The delegate call urlSession (_: taskIsWaitingForConnectivity 🙂 may not work 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 – Known Issues

  • The use of the Note Search can lead to unexpected results. (48238242)
  • If you use the Lasso tool to select colored character strokes and then rotate your device to landscape mode, the dashes will return to black. (54246012)

PencilKit Known Issues

  • If your app links to PencilKit, please do not try to send it to the App Store until further notice. (53811027)

Reality Kit Known Issues

  • Reality files with object anchors are not anchored to these objects in AR Quick Look or in applications. (53689364)
  • The camera feed remains visible at the base of objects loaded from a reality file when ARView.Environment.Background on ARView.Environment.Background.skybox (_ 🙂 (53715030) – Workaround: Disable Ground Shadows when setting the background to ARView.Environment.Background.skybox (_ 🙂 by setting ARView.RenderOptions to disableGroundingShadows.

Screen time – Known issues

  • If you enable multi-device sharing, the screen time settings will not sync 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

  • Shortcut automations are temporarily unavailable. (53182885)
  • The supportedOnDeviceRecognition property always returns false on the 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 may no longer be usable on iOS 13 Device with iOS 12 (50873839) Workaround: Disable iCloud Synchronization between devices running iOS and iPadOS 13 Beta and devices using iOS 12.
  • Currently, INSearchForMediaIntent.continueInApp is the only supported response for INSearchForMediaIntentResponseCode. (51010311)

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 by @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's request is now willChange instead of didChange and should now be sent before the object changes instead of being 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 you create a navigation view – the first is the master and the second is the detail. Example:

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

Swift Known Issues

  • Image instances Do not use Resizing information configured in asset catalogs. Instead, reconfigure the size of an image with the modifier resizable (capInsets: resizingMode :). (49114577)

Swift – Obsolete

  • In earlier versions of iOS 13 Beta, obsolete SwiftUI APIs were removed. (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 outdated 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 (element: element) -> bool {
get {contains (element)}
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 data to a Chromecast device. (51334673)

UIKit – New Features

  • The UITableViewCell class no longer changes the backgroundColor or isOpaque properties of the contentView and its subviews when cells are highlighted or selected. If you set an opaque background color for subviews of the cell inside (and including) the content view, this 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 autosize cells in a UITableView by overriding sizeThatFits (_ 🙂 without using the automatic layout, the height that you return is interpreted as the height you want for the content view of the cell, and UITableViewCell automatically adds any additional height needed to make room for the cell separator. If you implement manual resizing in this way, the contentView width of the cell is guaranteed to be accurate so you can use it in manual layout calculations when sizeThatFits (_ 🙂 is called for the UITableViewCell. (39742612)
  • In feature environments such. For example, views and view controllers, the traitCollection property is now populated with properties during initialization. These initial features represent a prediction of the final features that the feature environment receives when added to the hierarchy. Because the features that are populated during initialization are only predictions, they may be different from the features that are actually received in the hierarchy. 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. Vermeiden Sie daher, die Arbeit zu wiederholen, wenn dies nicht erforderlich ist. (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)

Watch – Bekannte Probleme

  • Nach der Aktualisierung auf iOS 13 Beta verschwinden möglicherweise Komplikationen bei 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 – Bekannte Probleme

  • Bei Verwendung des Simulators werden gespendete Verknüpfungen möglicherweise nicht in der Suche angezeigt. (50832782) Problemumgehung: Testen Sie auf einem Gerät mit aktivierten Einstellungen> Entwickler> Zuletzt verwendete Verknüpfungen anzeigen.
  • Wenn Sie die Lautstärke in Simulator ändern, während in Safari ein Video abgespielt wird, wird der Ton stummgeschaltet. (51207286)

Sie können sich über die Betasite von Apple anmelden, das Konfigurationsprofil herunterladen und installieren und dann drahtlos aktualisieren. Wenn Sie das Profil bereits haben, gehen Sie zu Einstellungen -> Allgemein -> Software-Update, um die Installation des neuesten Beta-Builds zu starten, oder Sie können warten, bis es automatisch installiert wird, wenn "Automatische Updates" aktiviert ist.


Source link