Search results for

iPadOS 17.7.7

3,646 results found

Post

Replies

Boosts

Views

Activity

Tunnel connection failed
Problem Many developers run into a persistent “Tunnel connection failed” error when trying to connect an iPad or iPhone for debugging. Even after reconnecting USB-C or Lightning and tapping “Trust This Computer” multiple times, the connection won’t establish. The issue isn’t on the Mac — it’s the iPad not activating its tunneled connection properly. What I discovered The iPad’s Developer Mode networking stack can become unresponsive. By enabling a few developer networking options and running the “Test Responsiveness” function, the system restarts the underlying network daemons and reopens the tunnel instantly. No reboot, no re-pairing, no resets required. Prerequisites iPad with Developer Mode enabled iPad and Mac on the same Wi-Fi network (or paired once via USB for trust) Xcode compatible with your iPad’s iOS version Steps to fix On your iPad, open Settings → Developer. Scroll to Networking and turn on: Network Link Conditioner → On Network Override → On Under the same Networking section, tap Responsiveness
0
0
43
Nov ’25
Reply to 'tabViewBottomAccessory' leaves an empty accessory area when conditionally hidden
So as @andepopande pointed out above based on the first version of Xcode 26.2 beta we shall have a fix that seems backwards compatible with 26.1. extension View { func apply(@ViewBuilder _ block: (Self) -> V) -> V { block(self) } } TabView { // Some tabs } .apply { if #unavailable(iOS 26.1) { // Previous approach that stopped working in iOS/iPadOS 26.1 $0.tabViewBottomAccessory() { if viewModel.showAccessoryView { // accessory content } else { EmptyView() } } } else { // When compiled with Xcode 26.2+ for iOS/iPadOS 26.1+ $0.tabViewBottomAccessory(isEnabled: viewModel.showAccessoryView) { // accessory content } } } I have tested and so far not seen the deeper problems within the tab content view stack I reported above.
Topic: UI Frameworks SubTopic: SwiftUI
Nov ’25
iPadOS 26.1: new issue with traitCollection when changing dark mode
Since iPadOS 26.1 I notice a new annoying bug when changing the dark mode option of the system. The appearance of the UI changes, but no longer for view controllers which are presented as Popover. For these view controllers the method traitCollectionDidChange() is still called (though sometimes with a very large delay), but checking the traitCollection property of the view controller in there does no longer return the correct appearance (which is probably why the visual appearance of the popover doesn't change anymore). So if the dark mode was just switched on, traitCollectionDidChange() is called, but the traitCollection.userInterfaceStyle property still tells me that the system is in normal mode. More concrete, traitCollection.userInterfaceStyle seems to be set correctly only(!) when opening the popover, and while the popover is open, it is never updated anymore when the dark mode changes. This is also visible in the standard Apps of the iPad, like the Apple Maps App: just tap on the map icon at th
3
0
384
Nov ’25
Reply to How to sending capability requests.
I have a new question: I include Capabilities in the Provisioning Profile that might not be used, just in case. If I don't list all these Capabilities in the driver's Entitlements, will it cause the driver to behave abnormally? No, this doesn't affect anything. I then created a UserClient inheriting from the IOUserClient class to access it from the app, but IOServiceOpen fails with code 0xe00002d7 and cannot open. Huh. So, 0xe00002d7 is kIOReturnOffline, but I'm not sure how you'd get it from IOServiceOpen. It's returned in a few places in DriverKit and xnu, but none of them look like places you'd reach from IOServiceOpen. My best guess is that you're either trying to open the wrong object or your subclass is in an odd/unexpected state which is making it non-connectable. If you haven't already, make sure you check the system log as it's possible we logged additional info about what actually happened. Actually... real-time correction of myself: And in the driver's Info.plist, the following definitions are spec
Nov ’25
Reply to Xcode 26.1 RC issue
@Martin81 I get the ReportCrash issue running an iOS 26.1 simulator such as an iPhone 17 Pro. And it is showing a wallpaper. The only sims that don't show a wallpaper in my case are iPad simulators running iPadOS 26.1. But here's what's really weird. I ran the Photos app in the iPhone 17 Pro simulator (which is showing the default wallpaper and causing high CPU). While viewing one of the stock simulator photos I chose Use as Wallpaper. I went through the steps. Even though the chosen image is now appearing as a black wallpaper, it did fix the high CPU problem for that simulator. Such a strange set of bugs.
Nov ’25
Reply to Assistance Needed: Accessing Smartcard Certificates for Document Signing on iOS
We were able to confirm that this setup works on macOS, but does not work on iOS/iPadOS. Our goal is PKCS#11-style certificate signing using USB hardware tokens. On macOS, the token is recognized through TKTokenWatcher, and we are able to obtain a usable SecKey via CryptoTokenKit and perform signing successfully. However, on iOS, although the token is detected as a smart card, we are not able to access the private key for signing: TKTokenWatcher does not report the token SecKeyCreateWithData does not produce a usable signing SecKey The smart card appears in TKSmartCardToken slots, but when sending APDU commands, the token returns 6985 / CACC errors (security status not satisfied) If there is an officially supported iOS-level workflow for accessing and using a private key on a USB smart card for signing, we would appreciate documentation or guidance.
Topic: App & System Services SubTopic: Hardware Tags:
Nov ’25
CryptoTokenKit: TKSmartCardSlotManager.default is nil on macOS (Designed for iPad) but works on iPadOS and macOS
I have an iOS/iPadOS app and 'm trying to communicate with usb smart card reader using CryptoTokenKit on all platforms (ios/ipados/macos). Minimal Repro Code import CryptoTokenKit import SwiftUI struct ContentView: View { @State var status = var body: some View { VStack { Text(Status: (status)) } .padding() .onAppear { let manager = TKSmartCardSlotManager.default if manager != nil { status = Initialized } else { status = Unsupported } } } } And my entitlement file has only one key: com.apple.security.smartcard = YES Behavior • iPadOS (on device): status = Initialized ✅ • macOS (native macOS app, with the required CryptoTokenKit entitlement): status = Initialized ✅ • macOS (Designed for iPad, regardless of CryptoTokenKit entitlement): status = Unsupported → TKSmartCardSlotManager.default is nil ❌ Expectation Given that the same iPadOS build initializes TKSmartCardSlotManager, I expected the iPad app running in Designed for iPad mode on Apple silicon Mac to behave the same (
2
0
215
Nov ’25
Reply to How to detect "Full Screen Apps" vs "Windowed Apps" multitasking?
There's no macOS-like menu bar when the user chooses Full Screen Apps. I didn't know this and some of my app's functionality can only be accessed through the main menu bar. So I was thinking I could show some alternative way to access those features when in that mode. iPadOS has supported the ability to open a new scheme through drag and drop using UIDragItem and NSItemProvider and dragging it to the edge of the screen. When a user chooses Full Screen Apps, this no longer works for opening a new scene. I'd like to disable the drag and drop if it's not going to actually do anything. Those are two main things I can think of so far that depend on the user's choice of multitasking mode.
Topic: UI Frameworks SubTopic: UIKit Tags:
Nov ’25
How to detect "Full Screen Apps" vs "Windowed Apps" multitasking?
I have an iPad app that supports multiple scenes. I discovered some issues with my app's user interface that I would like to tweak based on whether the user has setup multitasking (in iPadOS 26) as Full Screen Apps or Windowed Apps. Is there any API or way to determine the current iPadOS 26 multitasking setting? I've looked at UIDevice.current.isMultitaskingSupported and UIApplication.shared.supportsMultipleScenes. Both always return true no matter the user's chosen multitasking choice. I also looked at UIWindowScene isFullScreen which was always false. I tried to look at UIWindowScene windowingBehaviors but that was always nil.
4
0
238
Nov ’25
Reply to Xcode 26.1 RC issue
Are all of you posting bug reports with Feedback Assistant? Make sure you do. Be sure your report includes the steps needed to reproduce the issue and include the sysdiagnose attachment. What version of macOS is everyone seeing this issue with? In my case I'm running macOS 26.0.1. I don't know if the version of macOS matters or not. I see the issue with both Xcode 26 and Xcode 26.1. It's just requires starting an iOS/iPadOS 26.1 simulator. I have no issue when running an iOS/iPadOS 26.0 simulator.
Nov ’25
Core Bluetooth and app background launch
TN 3115 states that apps that do not use AccessorySetupKit will loose the ability to launch into the background to service bluetooth in iOS26. Starting in iOS 26 and iPadOS 26, only apps that use AccessorySetupKit to setup Bluetooth accessories will be relaunched. Is there any more information regarding this? Will it affect any app under iOS26 or only those build against the iOS26 SDK? My app (dev build) is still relaunched, even though I'm running iOS26, so I wonder if there are any more conditions checked.
1
0
160
Nov ’25