When trying to use a UISearchController setup with a UISearchBar that has scope buttons, the search controller's scopeBarActivation property is set to .onSearchActivation, the navigation item's preferredSearchBarPlacement property is set to .integrated. or .integratedButton, and the search bar/button appears in the navigation bar, then the scope buttons never appear. But space is made for where they should appear. Some relevant code in a UIViewController shown as the root view controller of a UINavigationController: private func setupSearch() { let sc = UISearchController(searchResultsController: UIViewController()) sc.delegate = self sc.obscuresBackgroundDuringPresentation = true // Setup search bar with scope buttons let bar = sc.searchBar bar.scopeButtonTitles = [ One, Two, Three, Four ] bar.selectedScopeButtonIndex = 0 bar.delegate = self // Apply the search controller to the nav bar navigationItem.searchController = sc // BUG - Under iOS/iPadOS 26 RC, using .onSearchActivation results in the sco
Search results for
iPadOS 17.7.7
3,647 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Are there known compatibility issues for apps built with Xcode 10 and Objective-C when running on iOS 26? There isn't a generalizable answer to this question. Xcode 10 shipped with the iOS 12 SDK, so you're jumping 7 major releases of iOS, as well as the developer tools, and so a lot has changed in that time frame. The only way to see how your app is affected is to build with the iOS 26 SDK and begin testing. Are there specific deprecated APIs or changes in iOS 26 that we should be aware of? There are two that you need to be aware of that will affect your app in the future, regarding adoption of the UIScene lifecycle, and if you support iPadOS, deprecation of UIRequiresFullScreen. We have Technotes for each: TN3187: Migrating to the UIKit scene-based life cycle TN3192: Migrating your iPad app from the deprecated UIRequiresFullScreen key Beyond that, you should raise your apps minimum deployment target to the currently recommended value of iOS 15 (or higher), and then rebuild your app to see what othe
Topic:
App Store Distribution & Marketing
SubTopic:
General
Tags:
Thanks, @yellow8 . I've double-checked the top-left corner, but the multiply.circle button isn't appearing for me on iPadOS. Is it possible that the presentation style or another setting affects its visibility? iPadOS 26 iOS 26
Topic:
UI Frameworks
SubTopic:
UIKit
Tags:
Hi, it seems like using Table on iPadOS 26 results in the table header not applying a background. When comparing the same code on iPadOS 18, the table header applies a blur behind the header to ensure legibility when the user scrolls the content. Is there a way to ensure Table applies a background effect to the header so that content remains legible during scrolling? Here is a minimal example: struct TablePreviewContent: Identifiable { var id: Int { text.hashValue } var text: String } #Preview { let content = [TablePreviewContent(text: Hello), TablePreviewContent(text: World)] Table(content) { TableColumn(Title, value: .text) } } I've attached screenshots of the behavior on iPadOS 26 compared to iPadOS 18 to illustrate the issue.
If the NavigationSplitView on iPadOS 26 is combined with a .inspector column, the sidebarToggle is always hidden, when the sidebar is collapsed. If you remove the .inspector modifier, the sidebarToggle stays visible throughout the collapsed or expanded state. Has maybe someone a workaround for this issue? The problem does not exist in iOS 18. The bug is reported as FB20061260
Sadly none of these issues are resolved in iPadOS 26 RC. I’m really disappointed in how Apple has ignored such glaring issues for 3 months despite bug reports being filed with trivial demonstration apps provided. I’m going to be embarrassed to release my app update with iOS 26 support (these aren’t the only long unfixed iOS 26 bugs affecting my app). Please Apple, take more pride than this.
Topic:
UI Frameworks
SubTopic:
UIKit
Tags:
App Icon created with Icon Composer is empty for visionOS app We are developing a universal app, and the app’s icon was created using Icon Composer. Xcode 26, RC visionOS 26 and visionOS 2.5 App Icons on macOS, iOS, and iPadOS are correct We have archived the app for macOS and iOS and successfully uploaded it to the App Store. This strongly suggests that the App Icon configuration in our project settings is correct for these platforms. App Icon issue on visionOS However, the visionOS app icon is not working as expected: When testing on the Vision Pro simulator (versions 2.x and 26.0), the app icon appears empty. When archiving and submitting to the App Store, the process fails with the following error: The app’s Info.plist file is missing the CFBundleIcons.CFBundlePrimaryIcon key for the visionOS App Icon. This suggests that the project’s App Icon settings may not be correctly applied for visionOS builds. Request for assistance We are preparing to release our app, one of the first to support Liquid G
The Cancel button for VNDocumentCameraViewController is not displayed on iPadOS 26. This issue appears to be specific to iPad, as the button appears correctly on iPhone.
According to Accessory Design Guidelines iPadOS support HID trackpad. Is there a design example of such supported devices? I have tried to adapt device software to guidelines without any result on iPad.
Topic:
App & System Services
SubTopic:
Hardware
(Re: previous answers - skip if you haven't followed the saga) Adding some context for the answer. I added AppKit specifically because it's not UIKit, as I didn't want an answer for iOS or ipadOS, but macOS. The only SwiftUI line is the onDrag, that I faithfully added to the line as the caller, but I didn't think I'd have a different DropHandler for macOS and ipadOS, the culprit seemingly being the onDrag SwiftUI part that tries to give me only the good thing on macOS, but somehow is unusable. As I repeated, I wanted to quickly iterate and used the hacks instead of trying to use the Async versions, where some versions aren't actually available. The final code will be in Async, thank you. My first SwiftUI app was with GCD because there wasn't an alternative back then. There's one now. But I'm also butting heads with SwiftData, where models cannot be Sendable, but Async are also required to be sendable, so I've had a lot of fun on this topic. With the nearly 200 trials I had to do in order to
Topic:
UI Frameworks
SubTopic:
AppKit
Tags:
We have observed an internet access issue after the device enters idle mode on iOS 26 beta 9. Although the Ivanti Secure Access Client appears connected, users are unable to access any resources (internet or intranet) after unlocking the device from idle. When we check the log socket connection looks not disrupted, packets are tunnelled but no resource access. Split tunnel enabled and proxy PAC configured. This was observed on both iOS and iPadOS 26 beta. Steps to reproduce: Connecting to the internet, launching the Ivanti client, locking the device, and then unlocking it after a brief period of idle. The issue occurs when the VPN remains connected but no resources are accessible.
As requested, we updated FB16131472 to show the asCopy:YES variant is still broken on iPadOS 18.6.2. Perfect, thank you. I think you'll be better always be better off doing the copy yourself (for example, that will let you provide better progress data), but I'm optimistic that this will be fixed in the near future. __ Kevin Elliott DTS Engineer, CoreOS/Hardware
Topic:
UI Frameworks
SubTopic:
UIKit
Tags:
I just opened a bug report on this issue, FB20094470. This issue impacts my app. I read the docs and understand that the search bar Cancel button should not appear on iPadOS. However, in my app, without explicitly setting any cancel button property on the search controller or search bar, a Cancel button has automatically appeared and functioned as expected on iPads from iOS 5 through iOS 18. Just say'n. But I can live without it.
Topic:
UI Frameworks
SubTopic:
UIKit
Tags:
In iOS and iPadOS 26 beta 9 (and previous batas), setting the tintColor property on a navigation bar does not tint bar button items. The text and images are always black in the following cases: Buttons displaying only text (initWithTitle:) Buttons displaying only a symbol (initWithImage:) Buttons displaying system items, ie., UIBarButtonSystemItemCancel. Nav bar title The tintColor seems to be respected for: Selected-state background for buttons configured with changesSelectionAsPrimaryAction. To reproduce, Create a UINavigationController, Add bar button items to its navigation item, Set a tint color as in the following statement: self.navigationController.navigationBar.tintColor = [UIColor redColor]; Then note that the bar button items are black rather than red as expected. I have filed a feedback: FB19980265.
Topic:
UI Frameworks
SubTopic:
UIKit
We recently updated our app to utilize the work-around suggested by Kevin Elliott. We're happy to report this work-around operates correctly with a USB drive on an iPad running iPadOS 18.6. Thus, we marked his answer as accepted. Specifically, our app now uses asCopy:NO when initializing UIDocumentPickerViewController. Our code then calls NSFileManager, which copies the selected file as a security-scoped resource to a local (i.e., private) folder in NSTemporaryDirectory(). Our app then processes this local file as before. We added a new phase to the beginning of our progress meter, which informs the user their selected file is being copied to the device. We appreciate Kevin's insight on this topic and his ability to point us in the right direction! As requested, we updated FB16131472 to show the asCopy:YES variant is still broken on iPadOS 18.6.2.
Topic:
UI Frameworks
SubTopic:
UIKit
Tags: