Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Apple Seeds Second Betas of iOS 16.4 and iPadOS 16.4 to Developers

MacRumors

MacRumors

macrumors bot
Original poster
Apr 12, 2001
68,120
38,875


Apple today seeded the second betas of upcoming iOS 16.4 and iPadOS 16.4 updates to developers for testing purposes, with the software coming two weeks after the launch of the first betas.

iOS-16.4-Feature-Blue.jpg

Registered developers are able to download the iOS 16.4 and iPadOS 16.4 updates over-the-air after installing the appropriate profile from the Developer Center. Going forward, beta updates will not require a profile and will instead be done directly on device through an Apple ID linked to a developer account. Note: There appears to be an issue with the iOS 16.4 beta 2 update that is preventing some developers from seeing it at the current time.

iOS 16.4 and iPadOS 16.4 add new emoji characters, including shaking head, pink heart, light blue heart, donkey, moose, jellyfish, hyacinth, ginger, black bird, and more. There are 31 new emoji in total, including left and right hand options in several skin tones.

Safari Web Push notifications have been added on the iPhone and iPad, and you can receive them from websites that have been added to the Home Screen on your device. Web Push notifications are identical to the notifications that you get from websites on the Mac, and behave like any other iOS notification.

Third-party browsers like Chrome are now able to let users add websites and websites to the Home Screen, and Apple has reintroduced the HomeKit architecture upgrade. There are also changes to Podcasts, minor updates to Apple Music, new options for Shortcuts, and more, with a full list of new features in iOS 16.4 and iPadOS 16.4 available in our features guide.

Article Link: Apple Seeds Second Betas of iOS 16.4 and iPadOS 16.4 to Developers
 
Article Link
https://www.macrumors.com/2023/02/28/apple-seeds-ios-16-4-beta-2-to-developers/
Last edited:
  • Love
Reactions: sorgo †
Exactly One year from today! See below. 👇👇

www.macrumors.com

Spring Apple Event Invites Could Be Sent Out Tomorrow

Update: We now have invites for a March 8 event! Apple uncharacteristically sent them out less than a week ahead of the event. Invites for...
www.macrumors.com www.macrumors.com

I'm happy Apple released a new iOS 16.4 Beta 2 today. Let's get it! 🔥
 
  • Like
Reactions: _Spinn_, SFjohn, BigMcGuire and 2 others
For those that do not have a developer account: Do you even see the "Developer Beta" as a selectable option in the Software update settings or can you only select "Public Beta" or nothing?

In my case I have my personal account (not developer) as the primary Apple ID of the device, but use my work account (developer) in TestFlight etc. on the same device. And I do see the Developer Beta option and do not have any warnings about not being eligible to enroll.
I wonder if personal accounts associated with developer accounts can still use the developer betas. If not, it is a headache for everyone who likes to keep their personal and work accounts separate.
 
It took 5 more minutes and showed for iphone that had personal IOS user checked for beta and ipad on developer (long time apple seed member) Dowloading on both right now
 
  • Like
Reactions: TheYayAreaLiving 🎗️
pacificblue said:
For those that do not have a developer account: Do you even see the "Developer Beta" as a selectable option in the Software update settings or can you only select "Public Beta" or nothing?

In my case I have my personal account (not developer) as the primary Apple ID of the device, but use my work account (developer) in TestFlight etc. on the same device. And I do see the Developer Beta option and do not have any warnings about not being eligible to enroll.
I wonder if personal accounts associated with developer accounts can still use the developer betas. If not, it is a headache for everyone who likes to keep their personal and work accounts separate.
Click to expand...
I use the public beta and I don’t have a developer account.
I still see all three options, off, developer beta, and public beta.
I assume it’ll be tweaked before the final release though, so people without the developer account don’t see the option for developer beta’s.
 
jsamuels said:
I have a dev account. Here's what I'm seeing. Maybe it will straighten itself out.
View attachment 2166057
Click to expand...
I had that message on phone so selected personal user and 5 minute later it works but left as developer on ipad and it also worked 5 minutes later. I am appleseed member for years so I think that is some kind of developer mode anyway it worked.
 
  • Like
Reactions: BigMcGuire and TheYayAreaLiving 🎗️
  • Haha
Reactions: theinsaneworld and TheYayAreaLiving 🎗️
It is always taking a few minutes for the upgrades to propagate through the systems. Mine just showed up a few seconds ago. Developer account, Dev Beta turned on and profile installed.
 
Public beta user here, curiously, if you go into the settings and select “ iOS 16 developer beta’s” it’ll let you download and install Beta 2 right now, even without a developer account.
Obviously this is probably going to be fixed by the time of final release, but it’s interesting.
I’m personally waiting until tomorrow though…
 
  • Like
Reactions: Sportpoz and KurtWilde

Backup and Restore​

Known Issues​

  • Watch migration might fail when restoring a backup to a new phone. (105416351)
    Workaround: Unpair the watch from the source phone, then pair it to the destination phone.

Beta enrollment for iPhone and iPad​

New Features​

  • Beginning with iOS & iPadOS 16.4 beta, members of the Apple Developer Program will see a new option to enable developer betas directly from Software Update in Settings. This new option will be automatically enabled on devices already enrolled in the program that update to the latest beta release. Your iPhone or iPad must be signed in with the same Apple ID you used to enroll in the Apple Developer Program in order to see this option in Settings. In future iOS and iPadOS releases, this new setting will be the way to enable developer betas and configuration profiles will no longer grant access. (101692915)

Core ML​

Deprecations​

  • Core ML Model Deployment is being deprecated. Consider using Background Assets or NSURLSession instead. (102993813)

Core Telephony​

Deprecations​

  • CTCarrier, a deprecated API, returns static values for apps that are built with the iOS 16.4 SDK or later. (76283818)

Home​

New Features​

  • Both manual and automatic Software Update support is now available for Matter Accessories. (102727759)

Known Issues​

  • The iOS device that initiates the pairing needs to be on the same iCloud account with the home hub. Only the owner of a home, not an invited user, can pair Matter accessories. (76012945)
  • You might receive an error when pairing a Matter accessory using the 11 digit setup code. (101554366)
    Workaround: Pair the accessory using the QR code instead.
  • When a manual software update is attempted on a Matter accessory with an available update, Home might not indicate that the update has been requested and continue to indicate an update is available. (104902918)
    Workaround: Check the Software Update pane in Home Settings at a later time, as the update might be taking place in the background.
  • The software update screen for Matter accsories might display the incorrect version number while an update is in progress. (105031569)
  • Right after pairing, an available firmware update is not offered in the Home app. (105757029)
    Workaround: Reboot all residents.
  • When there are multiple of the same accessory type updating to the same firmware or if there are back-to-back firmware versions for one accessory (during an incremental update), the new firmware update might not be offered. (105787380)
    Workaround: Reboot all residents or unpair the accessory and re-pair by clicking the “More options…” link to pair the accessory from there.

iCloud Drive​

Known Issues​

  • Filesystem APIs such as NSFileManager might trigger materialization of dataless files and/or directory structures in iCloud Drive, leading to hangs or performance problems for the calling application. (105009536)
    Workaround: Avoid calling anything which performs I/O on the main thread. Adopt UICollectionViewDataSourcePrefetchingand load cells asynchronously. I/O should be wrapped under -[NSFileCoordinator coordinateAccessWithIntents:queue:byAccessor:] to avoid blocking a thread on a synchronous call. Alternatively, opt out of this behavior by setting your IO policy to IOPOL_MATERIALIZE_DATALESS_FILES_OFFbut expect that I/O might fail with EDEADLK, if any component of the path is dataless (SF_DATALESS).
  • iCloud Drive might become unresponsive when opened from the Files app. (105438692)
    Workaround: Restart your device.

Keyboards​

New Features​

  • Updates to Keyboards include:
    • Support for new Unicode 15.0 Emoji.
    • Autocorrect for the Korean keyboard is enabled by default for testing and feedback.
    • Ukrainian keyboard now supports predictive text.
    • Gujarati, Punjabi, and Urdu keyboards add support for transliteration layouts.
    • New keyboard layouts are available for Choctaw and Chickasaw. (105243233)

MapKit​

Resolved Issues​

  • Fixed: Improved performance of MKOverlay objects. (102187262)

Pages, Numbers, and Keynote​

Known Issues​

  • When Advanced Data Protection for iCloud is turned on, Pages, Numbers, and Keynote might unexpectedly require collaborative documents to be closed. (103463223)
    Workaround: Close the affected document, spreadsheet, or presentation and reopen it after a few minutes.

Passkeys and Authentication Services​

New Features​

  • Web browsers on iOS with the com.apple.developer.web-browser entitlement now have passkey AutoFill within their WKWebView. This capability works without requiring any code changes or needing to rebuild. (97576198)
  • A new AuthorizationController API allows you to perform passkey and other types of authorization requests from SwiftUI views. (97576703)
  • A new WebAuthenticationSession API allows you to perform OAuthand other types of web-based authentication flows from SwiftUI views. (101259868)

Resolved Issues​

  • Fixed: AutoFill, including AutoFill for passkeys and passwords, now works with input elements contained in a Shadow DOM in web content. (103859657)
  • Fixed: Calling PublicKeyCredential.isUserVerifyingPlatformAuthenticatorAvailable() or PublicKeyCredential.isConditionalMediationAvailable() from a web page in a WKWebView now correctly returns whether passkeys can be used, based on the Associated Domains of the calling app. (104094169)

Known Issues​

  • Conditional mediation requests (passkey AutoFill) in web content don’t abort when their AbortSignal is fired. (99535627)

Pencil​

New Features​

  • Apple Pencil hover now provides Tilt and Azimuth support. (105412781)

Safari Web Extensions​

New Features​

  • Added support for modifyHeaders action type for declarativeNetRequest rules. (71867709)
  • Added support for browser.storage.session to store up to 10MB of data in-memory. (79283961)
  • Added support for persistent content scripts via browser.scripting.registerContentScript, browser.scripting.getRegisteredContentScripts, browser.scripting.unregisterContentScripts, and scripting.updateContentScripts. (91261369)

Resolved Issues​

  • Fixed browser.webNavigation events firing for hosts where the extension didn’t have access. Extensions should request host permissions for sites to receive events. (100204850)

SKAdNetwork​

Resolved Issues​

  • Fixed an issue where SKAdNetwork for Web Ads didn’t accept ad impressions. (104839712)

StoreKit​

New Features​

  • New StoreKit 2 APIs are available for promoted in-app purchases. Apps can receive promoted product purchase data from the App Store with PurchaseIntent.intents and can manage promoted order and visibility with Product.PromotionInfo. (85321849)

SwiftUI​

New Features​

  • A family of new view modifiers lets you build even richer resizable sheet experience with SwiftUI. Use these new modifiers to make the view behind a sheet interactive, provide a translucent background, control scrolling and expansion behavior, and even adjust the corner radius of the sheet.
    To let people interact with the content behind a sheet, use the .presentationBackgroundInteraction(_:) modifier. The following example enables people to interact with the view behind the sheet when the sheet is at the smallest detent, but not at the other detents:
    struct ContentView: View { @State private var showSettings = false
    var body: some View { Button("View Settings") { showSettings = true } .sheet(isPresented: $showSettings) { SettingsView() .presentationDetents( [.height(120), .medium, .large]) .presentationBackgroundInteraction( .enabled(upThrough: .height(120))) } } }
    Give your sheet a translucent background with the new presentationBackground(_:) modifier. The following example uses the thick material as the sheet background:
    struct ContentView: View { @State private var showSettings = false var body: some View { Button("View Settings") { showSettings = true } .sheet(isPresented: $showSettings) { SettingsView() .presentationBackground(.thickMaterial) } } }
    Add a custom view as the background of your sheet with the presentationBackground(alignment:content:) modifier.
    By default, when a person swipes up on a scroll view in a resizable presentation, the presentation grows to the next detent. A scroll view embedded in the presentation only scrolls after the presentation reaches its largest size. Use the new presentationContentInteraction(_:) modifier to control which action takes precedence.
    For example, you can request that swipe gestures scroll content first, resizing the sheet only after hitting the end of the scroll view, by passing the .scrolls value to this modifier:
    struct ContentView: View { @State private var showSettings = false
    var body: some View { Button("View Settings") { showSettings = true } .sheet(isPresented: $showSettings) { SettingsView() .presentationDetents([.medium, .large]) .presentationContentInteraction(.scrolls) } } }
    (101565636)
  • Apply the new .presentationCompactAdaptation(_:)modifier to the content of a modal presentation to control how it adapts to compact size classes on iPad and iPhone.
    For example, the popover modifier presents a popover on iPad. By default, a popover adapts to the narrow horizontal size class on iPhone by showing as a sheet. In the example below, the .presentationCompactAdaptation(.none) modifier asks SwiftUI to show this as a popover on iPhone as well.
    struct PopoverExample: View { @State private var isShowingPopover = false var body: some View { Button("Show Popover") { self.isShowingPopover = true } .popover(isPresented: $isShowingPopover) { Text("Popover Content") .padding() .presentationCompactAdaptation(.none) } } }
    Use .presentationCompactAdaptation(horizontal:vertical:) to adapt differently in horizontally and vertically compact size classes. (103257577)

Resolved Issues​

  • Fixed: ScrollView has improved support for right to left languages by default. If you have a ScrollView that shouldn’t change its behavior in right to left languages, use the .environment(\.layoutDirection, .leftToRight)modifier to ensure the ScrollView always sees a left to right layout direction. (65108729)
  • Fixed: Refreshable modifiers applied to lists will no longer also apply to lists or scroll views within the content of that list. Re-apply a refreshable modifier to the content of the list if this is desired behavior. (102052575)
  • Fixed: The no-argument presentationBackground() modifier has been removed. Use one of the overloads taking an explicit ShapeStyle or View instead. (105598868)

Deprecations​

  • TimelineView initializers that pass an instance of TimelineView<_, _>.Context into its content closure have been deprecated in this release, and replaced with equivalent versions that pass an instance of TimelineViewDefaultContextinstead.
    In TimelineView code that does not generate a warning, no action is needed: code that does not explicitly annotate the context type will use the new API when recompiled, without any change in functionality.
    In TimelineView code that does show this new deprecation warning, changing type annotations from TimelineView<_, _>.Context to TimelineViewDefaultContext will resolve the warning.
    This change improves the performance of compiling Swift and SwiftUI code. The new initializer uncouples the generic type of the TimelineView being instantiated from the generic type of the context passed into its content closure, avoiding the need for the compiler to reconcile those types during compilation. (100641618)
  • Several table initializers that were previously deprecated and replaced in iOS 16.2 and macOS 13.1 have now been removed from the API. Using these initializers will now generate a build error, with a Fix-It to switch to the replacement initializer API. For code that doesn’t generate this error, no action is needed.
    This change, along with other improvements in the Swift compiler, improve the performance of compiling Swift and SwiftUI code.
    The new, replacement API adds a parameter, of:, that identifies the type of the Table’s row values separately from the initializer’s row and column content closure parameters. This improves compilation performance in two ways. First, by knowing the row value type up-front, the compiler doesn’t need to infer that type from the body implementations of each closure. Second, the compiler can immediately enforce that each closure uses the same row value type in its body implementation, instead of needing to verify that the inferred types are equal after evaluating each closure.
    The following examples show code for creating a Table before and after adoption of the new API:
    // before (will now produce an error):Table { TableColumn("Name", value: \.name) TableColumn("Email", value: \.email)} rows: { ForEach(people) { person in TableRow(person) }}
    // after:Table(of: Person.self) { TableColumn("Name", value: \.name) TableColumn("Email", value: \.email)} rows: { ForEach(people) { person in TableRow(person) }}
    (102910184)

SwiftUI Navigation​

Resolved Issues​

  • Fixed: Navigation destinations nested within NavigationStackand NavigationSplitView are detected more performantly and reliably, no longer logging update cycles. (97597634)
  • Fixed: Navigation destinations that present a new view on top of a NavigationSplitViewColumn (rather than pushing a view onto a stack in that column) no longer cause an assertion failure on iOS or infinite loop on macOS when the destination view is itself a NavigationStack.
    For example, the below construction is functional
    NavigationSplitView { SidebarView() .navigationDestination(isPresented: $present) { NavigationStack { ... } }} detail: { ... }
    (103278180)
  • Fixed: Navigation destinations with data dependencies captured from ancestor views update more reliably.
    struct DataDependentNavigation: View { @State var changeColor: Bool = false @State var present: Bool = false
    var body: some View { NavigationSplitView { Color.blue .navigationDestination(isPresented: $present) { // This is a data dependency from an ancestor view changeColor ? Color.green : Color.yellow } } detail: { Color.teal }}
    (103429535)

Wallet​

Known Issues​

  • An error might occur when adding or presenting an ID card. (105302759)
 
I don't have a developer account... but it's letting me download the developer update. This must be a bug, right?

IMG_1367.PNG
 
  • Like
Reactions: srbNYC
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back