iPadOS 17.7.7

Hi, sorry to hear you're having issues with Apple Pay. Given you're using Apple Pay through a third party API (in this case Stripe's), you may need to reach out to them to determine the cause. To try and help, if you've confirmed Apple Pay on the Web is working on the same device with the same merchant identifier, then you should be able to rule out any issues with cards available on the device or the device region, and it suggests more of an issue with the underlying integration between the third party library and the native PassKit APIs. Because the Apple Pay sheet appears, and allows you to attempt to authorise a transaction, this should also rule out any entitlement or code signing issues for the app as well. It may be worth checking to see if the device is logging anything, which may provide some insight as to why it's failing. You can do this using Console on macOS with the device connected, and selecting it in the side menu. In particular, filtering on PassbookUIService should reduce most of the unnece

I’m having the very same issue. iPad Pro (11-inch) (2nd generation) iPadOS 26.1 Swift Playground 4.6.4 (1997.50)

The Declared Age Range APIs are available in iOS 26 or later. The iOS 26 SDK requires Xcode 26 or later as shown in Xcode Releases. Testing age assurance in the sandbox requires a device running iOS 26.2 beta or iPadOS 26.2 beta, and Xcode 26.2 beta 2.

Pease see Testing Age Assurance in Sandbox for more information. Testing requires using a device running iOS 26.2 or iPadOS 26.2 and a Sandbox Apple Account. Use isEligibleForAgeFeatures to determine whether a person using your app is in an applicable region that requires additional age-related obligations for when you distribute apps on the App Store. For more information, refer to Next steps for apps distributed in Texas.

This class below is my first attempt at determining if a device supports speech transcription. Any feedback on devices it works or doesn't work on would be appreciated! import Foundation import UIKit final class SpeechTranscriberSupportChecker { static let shared = SpeechTranscriberSupportChecker() private var cachedSupportsSpeechTranscriber: Bool? private init() {} func supportsSpeechTranscriber() -> Bool { if let cached = cachedSupportsSpeechTranscriber { return cached } let result: Bool if !isRealDevice() { result = false } else if !isRunningOS26orLater() { result = false } else { result = !isOnUnsupportedHardware() } cachedSupportsSpeechTranscriber = result return result } // MARK: - Checks private func isRealDevice() -> Bool { #if targetEnvironment(simulator) return false #else return true #endif } private func isRunningOS26orLater() -> Bool { let major = ProcessInfo.processInfo.operatingSystemVersion.majorVersion return major >= 26 } /// Devices that CAN run iOS/iPadOS 26 but DO NOT

This is now possible starting in the 26.2 updates of iOS, iPadOS, and visionOS which are currently available for testing. You'll want to install the latest seed and try out: SFSafariExtensionManager.getStateOfExtension( withIdentifier identifier: String, completionHandler: @escaping (SFSafariExtensionState?, (any Error)?) -> Void )

You should definitely file a bug about this. And please post your bug number, just for the record. When it comes to networking, Apple Vision Pro is much like an iPad. Do you see the same behaviour with your app running on iPadOS? Or, if you don’t have an iPad, on an iPhone with the WWAN disabled? One thing that’s specific to visionOS is that it has a few features that make heavy use of the Wi-Fi for real-time work. The ones that spring to mind are View Mirroring and Mac Virtual Display, but there are probably others. Real-time work will take priority of the bulk work done by a background session, so make sure you’re not using these features when running your speed tests. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com