- With iMessage Contact Key Verification, users can choose to further verify that they are messaging only with the people they intend. Contact Key Verification uses Key Transparency to enable automatic verification that the iMessage key distribution service returns device keys that have been logged to a verifiable and auditable map. When a user enables Contact Key Verification, they will be notified about any validation errors directly in the Messages conversation transcript and Apple ID Settings.
For even higher security, iMessage contact key verification users can compare a Contact Verification Code in person, on FaceTime, or through another secure call. They can also choose to create or edit a contact and save a public key to turn on CKV with that person.
All devices signed into your iCloud account must be on the minimum supported version of iOS 17.2 Beta, macOS 17.2 Beta, or watchOS 17.2 Beta. If you wish to keep using other devices on older versions of the OS, you will need to sign out of iMessage on these devices in order to enable contact key verification. (111356044)
- The Learn More links do not link to Knowledge Base articles during Beta. (101563811)
- When verifying another user, Contact Verification Code might not show if one user interrupts the flow. (114462363)
Workaround: Both users restart the process.
- After verifying a contact, the verificaton checkmark might not show up in Messages app. (116142336)
- Users might see an error to Turned Off transcript every few hours. (116405131)
Workaround: Dismiss the error.
- Users might see that they’re are not eligible to enable Contact Key Verification on some of their upgraded devices. (117044482)
Workaround: Retry after waiting at least 30 minutes.
- Unlocalized string shown for member count in the full screen Map View of Group Messages might appear (e.g. DETAIL_NUMBER_OF_PEOPLE_LABEL). (117287069)
- New pricing properties price, currency, and currencyCode are now available on Transaction. If an offer was applied to the transaction, a new property offer is available to see information about it (id, type, payment mode), as well as convenience properties offerID, offerType, and offerPaymentMode. (106650768)
Use _logChanges() to log causes of SwiftUI view updates.
Call the new debugging method `_logChanges()` in the body of a SwiftUI view to
log information about why the system is updating the view. For example:
struct MyView: View {
var body: some View {
#if DEBUG
let _ = Self._logChanges()
#endif
// … rest of view body …
}
}
As well as the physical property names, “@self” marks that the view value itself has changed, and “@identity” marks that the identity of the view has changed (that is, that the persistent data associated with the view has been recycled for a new instance of the same type).
The new `_logChanges()` method is like the existing `_printChanges()` one,
except that the new method uses the system console, which is useful in some debugging workflows.
Calls to `_logChanges()` log at the info level to the "com.apple.SwiftUI"
subsystem with the category “Changed Body Properties”. (113352555)
- Fixed: Resolved a possible Swift access conflict crash that could occur with toolbar items. (113992797)
- In widgets Text(_:style
does not animate its content by default. (107582710)
Workaround: To explicitly request an animation, use the View.contentTransition(_ modifier.
