“A Summary of the WWDC25 Group Lab”

In iOS 18, TabView with .tabViewStyle(.sidebarAdaptable) introduced a powerful adaptive pattern — tabs in compact, sidebar in regular. However, the current Tab API only supports a title and an image (icon). There is no way to provide a trailing accessory view (e.g., a secondary icon or indicator) for sidebar rows. This is a meaningful gap in the API, because trailing accessories are a well-established pattern throughout UIKit and SwiftUI. Precedent in Apple's own design language Apple already supports trailing accessories in many analogous contexts: UITableViewCell / UICollectionViewListCell — support accessories (disclosure indicators, checkmarks, custom views) via UICellAccessory. UIListContentConfiguration — allows leading and trailing content in list rows. SwiftUI List rows — support Label, HStack with trailing elements, .badge(), and swipeActions. NavigationLink — automatically renders a disclosure chevron as a trailing accessory. UITabSidebarItem (UIKit, iOS 18) — supports configurationUpdateHandler and

Hello, We are facing an issue with performing a DTLS handshake when our iOS application is in the background. Our app (Vocera Collaboration Suite – VCS) uses secure DTLS-encrypted communication for incoming VoIP calls. Problem Summary: When the app is in the background and a VoIP PushKit notification arrives, we attempt to establish a DTLS handshake over our existing socket. However, the handshake consistently fails unless the app is already in the foreground. Once the app is foregrounded, the same DTLS handshake logic succeeds immediately. Key Questions: Is performing a DTLS handshake while the app is in the background technically supported by iOS? Or is this an OS-level limitation by design? If not supported, what is the Apple-recommended alternative to establish secure DTLS communication for VoIP flows without bringing the app to the foreground? Any guidance or clarification from Apple engineers or anyone who has solved a similar problem would be greatly appreciated. Thank you.

When building in Xcode on MacOS Tahoe, it seems it is no longer possible to dynamically specify a small size toolbar for NSToolbar/NSToolbarItem. It works in MacOS code compiled and linked on earlier systems. I don't want to use SFSymbol, or templates. I have over 60 custom-made .png toolbars, in individual Image Set files, at the previous requisite sizes of 24x24 / 48x48, and 32x32 / 64x64. Sure -- I can configure an NSToolbar with whatever size .png assets I want. I just can't dynamically switch between the two groups of sizes. According to the Apple Coding Assistant, the only solution is to change the image names of each of the NSToolbarItems at runtime. OK -- but even when attempting that, the NSToolbarItems refuse to take on their smaller size... ...unless: they are attached to a custom view NSToolbarItem with an NSButton of style Bevel. I have about 10 of those, and YES -- I CAN change those to a small size. Is this REALLY what I'm forced to do?! The Apple Coding Assistant just runs me around i

I’m attempting to use a Locked Camera Capture Extension (created from Xcode’s template / following Apple’s “Creating a camera experience for the Lock Screen” guidance). The extension builds, embeds, and installs on a physical device, but I cannot get it provisioned with the required entitlement com.apple.developer.locked-camera-capture. Environment Xcode: 26.0.1 (17A400) iOS: 26.2.1 (device) Apple Developer Program: paid Individual (Team ID: FT55UW9363) Key issue: provisioning profile for the ExtensionKit appex lacks the locked-camera entitlement The locked camera capture target is embedded as an ExtensionKit extension: .../DirectionalCamera.app/Extensions/LockedCapture.appex I decoded the embedded provisioning profile inside that .appex and printed its Entitlements dictionary: security cms -D -i .../DirectionalCamera.app/Extensions/LockedCapture.appex/embedded.mobileprovision > /tmp/locked_profile.plist /usr/libexec/PlistBuddy -c Print:Entitlements /tmp/locked_profile.plist Entitlements present in the emb

iOS mTLS Client Certificate Authentication Fails in TestFlight with Error -25303 Problem I'm building an iOS app that uses mTLS (client certificates received from server at runtime). Storing SecCertificate to keychain fails with error -25303 in both development and TestFlight builds, preventing SecIdentity creation needed for URLSession authentication. Environment: iOS 18.2, iPad Pro, TestFlight internal testing, keychain-access-groups properly configured Diagnostic Results Testing keychain operations shows an interesting pattern: ✅ Generic Password - Works: let addQuery: [CFString: Any] = [ kSecClass: kSecClassGenericPassword, kSecAttrAccount: test, kSecValueData: password.data(using: .utf8)! ] SecItemAdd(addQuery as CFDictionary, nil) // Returns: 0 (success) ✅ SecKey - Works: let addKeyQuery: [CFString: Any] = [ kSecClass: kSecClassKey, kSecValueRef: privateKey, kSecAttrApplicationTag: tag ] SecItemAdd(addKeyQuery as CFDictionary, nil) // Returns: 0 (success) ❌ SecCertificate - Fails: let addCertQu

Hello, I'm trying to submit my first auto-renewable subscription for my app, but it shows Missing Metadata status and I cannot identify which field is incomplete. What I've completed: ✅ Product ID and Display Name ✅ Description ✅ Price: $4.99/month for 175 countries ✅ Duration: 1 month ✅ Localization (English): Display name and description filled ✅ Review Screenshot uploaded ✅ Review Notes provided ✅ Tax Category set ✅ Paid Apps Agreement signed and active ✅ Banking and tax info complete Common issues I've already checked: ✅ Subscription is part of a subscription group (Premium Features) ✅ At least one pricing tier is configured ✅ Localization has both display name AND description ✅ Review screenshot is provided ✅ Paid Apps Agreement is active (not pending) The Problem: Subscription status: Missing Metadata Localization status: Prepare for Submission Need it to show Ready to Submit to include with my app My Question: What field am I missing? I've checked all visible fields but the status won't change

Original Problem We use codesign and notarytool in a scripted environment to build and distribute binaries daily. We also do manual builds by logging into the build server using SSH. This has been working for many years, but after updating to a new Developer ID Application certificate, codesign was failing with errSecInternalComponent and the console logs showed errSecInteractionNotAllowed. Summary of Resolution Attempting to fix the problem resulted in multiple copies of the same Certificate which were NOT shown by Keychain Access. I had to run security delete-identity multiple times to clear out the redundant Identities and then imported the certificate using the security CLI tool. Details I originally followed these instructions for requesting and installing a new certificate: https://developer.apple.com/help/account/certificates/create-developer-id-certificates/ Tip: Use the security tool intead These instructions fail to mention two critical points: 1) they assume the machine you generate the re

I'm building a content filtering app using NEURLFilterManager and NEURLFilterControlProvider (introduced in iOS 26). The app uses a PIR server for privacy-preserving URL filtering. Everything works with development-signed builds, but App Store export validation rejects: Entitlement value url-filter-provider for com.apple.developer.networking.networkextension — not supported on iOS I have Network Extensions enabled on my App IDs in the developer portal, but the provisioning profiles don't seem to include url-filter-provider, and I don't see a URL filter option in the Capability Requests tab. What I've tried: Entitlement values: url-filter-provider, url-filter — both rejected at export Extension points: com.apple.networkextension.url-filter, com.apple.networkextension.url-filter-control — both rejected Regenerating provisioning profiles after enabling Network Extensions capability My setup: iOS 26, Xcode 26 Main app bundle: com.pledgelock.app URL filter extension bundle: com.pledgelock.app.url-filter PIR server

I see many developers struggling with ASO where AI written content does not deliver results, performance analysis is unclear, localization is ignored, App Store optimization is incomplete, and keywords are often poorly chosen. I am considering running two simple group sessions to share practical tips and show clear ways to improve ASO with real effort involved, and I would like feedback on this idea whether offered for a small fee or even for free.

Hi, I'm here hoping for some help or advice in terms of a critical situation I'm currently facing. I've submitted an iOS app more than one month ago, it was quickly got review and rejected twice, and when I re-submit the third time with new build, it then was stuck in the Waiting for review status for about 3 weeks. Then, I decided to withdraw the submission and re-submit again, but it doesn't work and remain Waiting for review status until now. During these waiting period, I’ve contacted Apple Support multiple times through mails, and received confirmation that my expedited review request was approved. However, no progress has been made since then. Here is a quick summary of the timeline Initial submission: July 29, 2025 Rejected due to Guideline 4.2.2 & 2.1: July 30, 2025 Second submission: Aug 4, 2025 Rejected due to Guideline 4.2.2 & 4.2.0: Aug 6, 2025 Third submission: Aug 6, 2025 Withdraw third & create forth submission: Aug 25, 2025 If anyone from the App Review team sees this post