All of these issues appear when the search controller is set on the view controller's navigationItem and the search controller's searchBar has its scopeButtonTitles set. So far the following issues are affecting my app on iOS/iPadOS 26 as of beta 7: When the scopeBarActivation of UISearchController is set to .onSearchActivation, the preferredSearchBarPlacement of the navigationItem is set to .integratedButton, and the searchBarPlacementAllowsToolbarIntegration is set to false (forcing the search icon to appear in the nav bar), on both iPhones and iPads, the scope buttons never appear. They don't appear when the search is activated. They don't appear when any text is entered into the search bar. FB19771313 I attempted to work around that issue by setting the scopeBarActivation to .manual. I then show the scope bar in the didPresentSearchController delegate method and hide the scope bar in the willDismissSearchController. On an iPhone this works though the display is a bit clunky. On an iPad, the scope bar does
Search results for
A Summary of the WWDC25 Group Lab
10,092 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
I'm working with SwiftData and SwiftUI and it's not clear to me if it is good practice to have a @ModelActor directly populate a SwiftUI view. For example when having to combine manual lab results and clinial results from HealthKit. The Clinical lab results are an async operation: @ModelActor actor LabResultsManager { func fetchLabResultsWithHealthKit() async throws -> [LabResultDto] { let manualEntries = try modelContext.fetch(FetchDescriptor()) let clinicalLabs = (try? await HealthKitService.getLabResults()) ?? [] return (manualEntries + clinicalLabs).sorted { $0.date > $1.date }.map { return LabResultDto(from: $0) } } } struct ContentView: View { @State private var labResults: [LabResultDto] = [] var body: some View { List(labResults, id: .id) { result in VStack(alignment: .leading) { Text(result.testName) Text(result.date, style: .date) } } .task { do { let labManager = LabResultsManager() labResults = try await labManager.fetchLabResultsWithHealthKit() } catch { // Handle error }
Hi @DTS Engineer We attempted to capture a fresh sysdiagnose, but we were unable to reproduce the issue in our lab. We will continue our efforts to replicate the problem. [quote='852684022, DTS Engineer, /thread/783870?answerId=852684022#852684022'] PushKit and CallKit should both be configured in applicationDidFinishLaunching. The goal here is that you want CallKit to be fully configured before your PushKit delegate is called to deliver a VoIP push. I would add an additional call to set the configuration before you call reportNewIncomingCall on the first push you receive, as this should ensure that callservicesd has a valid session ID. Note the configuration doesn't need to change, so setting the configuration to the existing value will work fine. [/quote] I believe our app shall have done this correctly, as both incoming and outgoing calls functioned properly before the problem occurred. Our application did not restart or reinitialize during this time. The issue does not happen on the first call(pu
Topic:
App & System Services
SubTopic:
General
Tags:
An Application Group with Identifier 'group.com.aaa.aaa.onesignal' is not available. Please enter a different string. How can I Fix this error? I need to add it in this format.
Topic:
App & System Services
SubTopic:
Notifications
Hello! The test report has received an overhaul as of Xcode 15. When you open your result bundle in your workspace, you'll be able to find the jump buttons to navigate to the source code in the test case details screen. To get to the test case details screen, you can double click on the corresponding failed test on the Summary screen, or by double clicking into the test in the Tests Outline screen. On either the activities tab or the runs tab, the jump button will appear when you hover over the callstack row. You can also navigate to the source by clicking on the View Source button in the header of the test case details screen. See the WWDC23 video Fix Failures Faster for a tour of the test report - https://developer.apple.com/videos/play/wwdc2023/10175/
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
If you haven’t already explored the Searching, displaying, and navigating to places sample code and the WWDC25 session: Go further with MapKit, those are excellent resources to help you get started.
Topic:
UI Frameworks
SubTopic:
SwiftUI
Tags:
According to the WWDC25 Presentation Track workouts with HealthKit on iOS and iPadOS, there is supposed to be a new property for restoring an active workout after a crash on iOS/iPadOS. The developer documentation also supports this. However, this property does not seem to exist in the latest Xcode 26 beta, even in projects targeting iOS 26.0 as the minimum version. Am I missing something? Has this property not been made available yet? It is actually looking like all of the new iOS 26.0 properties are missing UIScene.ConnectionOptions on my system.
On our paid Apple Developer Program account (role: Account Holder/Admin), the Call Directory capability toggle does not appear on any iOS App Extension Identifier we create. Because of that, provisioning profiles for those extension IDs never include the Call Directory entitlement and the extension cannot be enabled on device. That is the only reason we tried to add manually which does not work. Environment Membership: Apple Developer Program (paid, active) Xcode: [16.x] iOS devices tested: iOS 18.4.1, 18.5 and 18.6.1 App type: iOS app + Call Directory extension App Groups: enabled and working What I am not seeing In Certificates, Identifiers & Profiles → Identifiers → (iOS App ID, type App Extension), I expect to see a Call Directory capability toggle I can enable but it is not there What actually happens The Call Directory toggle is missing from the extension Identifier details page. Profiles created for the extension ID don’t contain the Call Directory entitlement. The extension never appears
Topic:
Code Signing
SubTopic:
Entitlements
Tags:
There is no option for fixing this. Per the documentation [1], if you have an macOS app that’s ever shipped with an app group, you can’t transfer it. That’s an annoying limitation, and it’d be reasonable for you to file a bug requesting that the limitation be lifted, or perhaps limited in some way. But, right now, you simply can’t transfer such an app. If you do file a bug about this, please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] App Store Connect Help > Transfer an app > App transfer criteria
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
Sadly there is not much change in SwiftData in WWDC25 while fatal issues like this one must be fixed as soon as possible. Just to allow SwiftData works normally.
Topic:
App & System Services
SubTopic:
iCloud & Data
Tags:
@DTS Engineer Thank you, but I read all the threads and didn't find any options for fixing it. Electron likely set up this flag by default, since we didn't configure the app group. Can you give me some advice, especially for my case? Electron + JS application. Thank you so much.
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
It’s a documented limitation that Mac apps can’t be transferred if they ever used an app group. See the extended discussion on this thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
Feedback for iPhone and iPad – Display Technology Dear Apple Team, Currently, the mainstream display technology used in iPhone and iPad is OLED. However, OLED panels produce significant PWM flickering, which strongly irritates the human eye. Many users, especially in China, experience eye strain, tearing, and discomfort after using OLED devices for a period of time. There is a large group of users here who are highly sensitive to screen flicker and therefore cannot use OLED-based devices at all. What they truly need is an eye-friendly device with either LCD or flicker-free Mini-LED display technology. I sincerely recommend that Apple consider offering iPhone and iPad models with LCD or Mini-LED panels. Such displays could provide better eye comfort, no flicker, and a healthier experience. Currently, almost no smartphone manufacturers in China provide such options, and even if they do, their devices often come with outdated chipsets and cannot be used as a reliable daily driver. This presents a valuab
I added a extension called Call Directory to an IOS app as we want to call blocking and caller id. I was able to add App Groups to both runner and CallDirectory. I cannot see of add Call Directory capability. Am I missing something. I added the extension through the Call Directory Target template. If I try to add this to CallDirectory.enitlements manually com.apple.developer.callkit.call-directory call-blocking caller-identification i recieve this signing error. Provisioning profile iOS Team Provisioning Profile: doesn't include the com.apple.developer.callkit.call-directory entitlement. I cannot add Call Directory to an identifier in Apple Developer either.
Im seeing the same thing, started on 2025-08-13. Newly pushed build were no longer being added to an Internal Testing group (configured for automatic distribution)
Topic:
App Store Distribution & Marketing
SubTopic:
TestFlight
Tags: