You can achieve this with the following code in your view controller: navigationItem.style = .editor // Left align title view navigationItem.titleView = titleLabel

@Technology Evangelist Sure thing, FB24864715: ToolbarSpacer(.fixed) doesn’t separate ToolbarItem and ToolbarOverflowMenu Liquid Glass backgrounds

Looking over documentation, the only thing I’ve uncovered for moving custom views is “get an array of UIView.ReservedRegion instances from reservedRegions(kind:options:). Inspect the frames of the reserved regions, and adjust your views accordingly.”

FB24914585: Unable to achieve correct horizontal margins/padding insets on iPhone Duo with SwiftUI

I had the user collect more diagnostics on the AppStore.sync() error: localizedDescription: Unable to Complete Request error: StoreKit.StoreKitError.unknown domain: StoreKit.StoreKitError code: 2 userInfo: [:] And device configuration: iOS 26.6.2 iPhone 17 Pro Max 101 GB of 256 GB Used Language: en Locale: en_US Calendar: gregorian Time Zone: US/Central -0500

@DTS Engineer Thanks for your response. What's strange is this code has worked for approximately 15,000 other purchases since I shipped it about 2 years ago (migrated to StoreKit 2 from the StoreKit 1 implementation I had in place for about 10 years prior), and it hasn't changed since, so I don't see any issue in my code. I'd like to learn why AppStore.sync() is throwing Unable to Complete Request as that may provide insight into what's going on with this unique issue that seems specific to this user's account/device configuration/history.

For apps that support both iOS 26 and iOS 27+, the recommended approach is to use a single AppIntent struct that adopts the OpenIntent protocol and is annotated with the @AppIntent(schema: .system.open) macro. Hi @DTS Engineer! In doing this, a compiler error appears: 'open' is only available in iOS 27.0 or newer, so it doesn't seem possible to achieve this recommended approach. If I annotate that struct @available(iOS 27.0, *) and duplicate the old one, renaming it, then building the project fails with error OpenIntent targets should be unique, but these all have 'MyEntity' as their target: 'OpenMyEntityIntent' and 'OpenMyEntityLegacyIntent'. Am I missing something?

The iOS 27 SDK exposes PHImageRequestOptions.preferHDR and PHLivePhotoRequestOptions.preferHDR. I don't see API to enable preferredImageDynamicRange on PHLivePhotoView unlike UIImageView. Even with UIImageView, I don't see photos in HDR after configuring options.preferHDR = true and imageView.preferredImageDynamicRange = .high.

In the App Store Connect iOS app, select an app, and choose Notifications. There’s toggles for Crash Feedback and Screenshot Feedback.

This sounds like the same or very similar issue I’ve reported on iOS 26. FB21449121: UIInputViewController: Custom keyboard extension height is incorrect depending on which keyboard you switched from when app has an input accessory view Start on the English system keyboard Tap and hold the globe key and switch to the third-party keyboard Notice the height and layout of the keyboard - take a screenshot Tap and hold the globe key and switch to the emoji keyboard Tap and hold the globe key and switch to the third-party keyboard Notice the height and layout of the keyboard - take a screenshot Compare the screenshots Expected: The screenshots should be identical Actual: The keyboard height is smaller when you came from the emoji keyboard due to losing insets from the top edge

Thanks Quinn! FB24179736

Yes, check out Sheets in the Human Interface Guidelines

I hope to see in-app purchase support added as well. I have a free app with a one-time non-consumable IAP to unlock all functionality. Several companies have reached out wondering how they can purchase it for their managed employee devices. Unfortunate to hear only subscriptions will be supported as I have no plans to require recurring payments from my customers, and I definitely do not want to maintain two different apps one paid upfront. FB10277182

I heard at one point AppShortcutParameterPresentation should address this, but was never able to get it to update. Is that incorrect?

Yes, it is resolved in iOS 26.5. Release Notes: Fixed: Transaction.currentEntitlements might be empty if a customer has an active subscription when the device’s system calendar is set to a non-Gregorian format. (173415174)