Team-scoped keys introduce the ability to restrict your token authentication keys to either development or production environments. Topic-specific keys in addition to environment isolation allow you to associate each key with a specific Bundle ID streamlining key management. For detailed instructions on accessing these features, read our updated documentation on establishing a token-based connection to APNs.

Hello developers! Thank you for your dedication to creating apps with great performance. We’re excited to kick off another year of partnering with you on improving power and performance in your apps. At WWDC26, check out the following new things in the latest platform SDKs and Xcode 27 beta for performance. You can also join us online for a Power and Performance Group Lab on Tuesday, June 9 at 11 AM Pacific. Meet State Reporting and the new MetricKit State reporting: The new StateReporting framework lets your application express its state to downstream tools like Instruments and MetricKit. Make your telemetry and traces much more useful by adopting this simple API. MetricKit: In the 27 releases, the Swift-first MetricManager API replaces the MXMetricManager API. Combined with State Reporting, the new MetricKit provides more granular metrics to isolate performance problems faster. It also provides a more expressive API that is great to use in Swift, with improved Swift concurrency and Codable support. With this year’s releases, the MXMetricManager API is considered legacy. ▶️ To learn more, watch Meet the new MetricKit. Discover new features in Xcode organizer Metric goals: Xcode organizer now provides a goal metric for Battery Usage, Disk Writes, Hang Rate, Hitches, Memory, and Storage metrics, allowing you to prioritize performance engineering across more areas. Generate recommendations: Quickly resolve the highest impact performance issues in your app by using Generate Recommendations for Crash, Energy, Disk Write, Hang and Launch diagnostics. Insights overview: The new insights overview in Xcode organizer summarizes high-impact performance regressions for metrics and diagnostic reports, helping you plan and prioritize performance engineering work. Storage metrics: Storage metrics are now available in Xcode organizer, allowing you to monitor your app's Documents & Data and App Size across releases and catch regressions in cache usage and bundle size. Hitches metric: The new Hitches metric replaces the Scrolling metric in the organizer and now displays hitches for all animations in your app, giving you a comprehensive view of animation performance. ▶️ To learn more about other advancements in Xcode, watch What’s new in Xcode 27. Improve app responsiveness with Instruments Foundation Models: The Foundation Models instrument is redesigned with a tree view that lets you drill into individual requests, inspecting tool call arguments and results, inference prompts and responses, and token statistics. Use it to understand caching behavior, measure latency, and optimize throughput. System Trace: System calls, VM faults, and thread states are now unified into a single plot, with a new blending algorithm that stays readable even at high density. Once you spot something worth investigating, left/right key navigation lets you follow a thread's activity step by step, and the inspector provides quick actions like pinning the thread that made another thread runnable. System Trace now also draws thread priority and QoS over time, making it easier to identify priority inversions and unexpected QoS degradations that affect responsiveness. Swift Concurrency: New Main Actor and Global Concurrent Executor tracks let you visualize running tasks and executor queue depth over time, making it easier to spot task scheduling delays and actor contention. Tasks are now grouped into collections for faster navigation. Swift Tasks, Actors, and Executors instruments can now surface Call Trees, Flame Graphs, and Top Functions scoped to each entity — so you can pinpoint exactly where concurrency overhead lives. Top Functions: Helper functions and runtime internals can be expensive but hard to spot in a standard call tree. The new aggregation mode in Top Functions surfaces any function's total execution time across the entire call stack, making it easy to identify and prioritize hidden hotspots. Run Comparison: Compare call tree data across builds to identify regressions and performance wins. Results can be explored as an outline, flame graph, or top functions — choose whichever view best fits your workflow. ▶️ To learn more about profiling your app with Instruments, watch “Profile, fix, and verify: Improve app responsiveness with Instruments” ▶️ To learn about Foundation Models optimization, watch “Debug and profile agentic app experiences with Instruments”. If you have any questions about using State Reporting or the new MetricKit, create a post on the forums. For help creating a post, see Tips on writing a forum posts.

We are looking to scale up our automated testing infrastructure for macOS development. Ideally, we want to create a large-scale testing farm capable of running parallel integration tests across multiple OS versions and configurations. However, we are running into a major roadblock with the Software License Agreement (SLA) limitation, which restricts the concurrent execution of macOS within virtualized environments to a maximum of two (2) instances per physical host. This restriction creates a massive bottleneck for high-end hardware. Investing in powerful machines like the Mac Studio or Mac Pro feels entirely inefficient for this use case; their massive core counts and memory capacities are effectively wasted if the host is legally throttled to just two concurrent VMs. Given this friction, we have a few questions for the community and any Apple engineers tuning in: are there any known plans, official updates, or historical precedents suggesting Apple might revise or remove this 2-VM limit for enterprise testing workflows? Any insights, policy updates, or architectural recommendations on building large-scale, compliant macOS test farms without underutilizing high-end hardware would be greatly appreciated. Thank you!

Hi, I am trying to use AAUSBAccessoryManager with mac os 27 to connect host usb device to guest vm. here is my code // // USBPassthroughManager.swift // VirtualProg import AccessoryAccess import Foundation import IOKit @available(macOS 27.0, *) class USBPassthroughManager: NSObject, ObservableObject, AAUSBAccessoryListener { static let shared = USBPassthroughManager() @Published var availableDevices: [AAUSBAccessory] = [] func startListening() async { do { let existing = try await AAUSBAccessoryManager.shared .registerListener(self, matchingCriteria: []) await MainActor.run { self.availableDevices = existing } } catch { LogManager.shared.log(vmName: AppConstants.logGeneral, type: .error, message: "USB passthrough listener failed: \(error.localizedDescription)") } } func usbAccessoryDidConnect(_ usbAccessory: AAUSBAccessory) { DispatchQueue.main.async { guard !self.availableDevices.contains(where: { $0.registryID == usbAccessory.registryID }) else { return } self.availableDevices.append(usbAccessory) print(self.displayName(for: usbAccessory)) } } The usb icon in status bar menu is displayed and i can select the the usb device to connect to my app. the usb device is connected to my app. it is shown in the status bar. but usbAccessoryDidConnect is not firing. i have the entitlement com.apple.developer.accessory-access.usb in the capabilities. i get this in the xcode console start failed ((iokit/common) not permitted) for plugin for .......... and also disconnect is also not firing. Not sure what i am doing wrong. How can i determine the name of the USB Device from AAUSBAccessory. Any help would be appreciated. Thanks

Xcode’s “App Thinning Size Report” reports a size under 15MB, but very close to it like 14.9MB, and if I publish the clip it becomes unavailable for costumers (They get "App Clip Unavailable" after scanning the QR code. On the other hand, if the size on the report is 14.7MB, it works fine for everyone. Can you advice a more accurate way to determine if the size is valid for distribution? On the same topic: Are there any plans to increase the size limit beyond the 15MB?

I am testing NEURLFilter on macOS using the SimpleURLFilter sample, and I am seeing a failure from neagent while it is saving the local URL prefilter Bloom filter to its mmap file. The relevant log is: neagent +[NEBloomFilter mmapToFile:data:dataLength:numberOfBits:numberOfHashes:murmurSeed:tag:]: NEBloomFilter - failed to open mmap file /private/var/db/urlPrefilter/com.apple.networkextension.url-prefilter-data.temp.com.example.apple-samplecode.SimpleURLFilterTC3Q7MAJXF <errno 13 - Permission denied> neagent <NEAgentURLFilterExtension: 0xc8ce64280>: -[NEAgentURLFilterExtension startURLFilter]_block_invoke - Failed to save first fetch of pre-filter data Environment: macOS: 26.5.1 (25F80) Xcode: 26.5 (17F42) Platform: macOS Signing type: Apple Development (automatically manage signing) What I am doing: Build and run the containing app. Save and enable the NEURLFilterManager configuration. The URL filter provider starts. The provider's prefilter code is reached. neagent logs the mmap failure above while trying to open a temporary file under /private/var/db/urlPrefilter. Expected result: neagent should be able to create or open its system-managed URL prefilter cache / mmap file under /private/var/db/urlPrefilter, and the local Bloom filter should be loaded successfully. Actual result: neagent fails to open the temporary mmap file with errno 13 Permission denied: /private/var/db/urlPrefilter/com.apple.networkextension.url-prefilter-data.temp.<bundle/team-specific suffix> I am not manually creating, modifying, or chmod/chown-ing /private/var/db/urlPrefilter or anything inside it. The directory and its contents are entirely system-managed. The failure appears to happen inside neagent while it is handling the system-managed URL prefilter cache. The failure occurs at the mmapToFile: step while neagent saves the Bloom filter prefilter data. Directory state: drwxr-xr-x 2 root wheel 64 /private/var/db/urlPrefilter Has anyone else encountered this? Any suggestions on what could cause neagent to fail with errno 13 on its own mmap file under /private/var/db/urlPrefilter?

We have an app that uses UDP messaging. It has been working for over 3 years successfully. The App is now failing on installation with MacOS26. The issue would appear to be that MacOS is silently blocking the UDP traffic. If we disable the local network for the App, and then turn back on, this will fix the issue. But this needs to be done on every system restart.

I am porting a project from the now deprecated dns_util api to use the DNS Service Discovery api. With dns_util I am able to specify a DNS name server to use for resolving queries. This is useful for testing new servers or propogation when changes have been made to DNS records. Is it possible to specify the nameserver to use with DNS Service Discovery?

Hi, I wanted to develop a small tool to launch Home Assistant OS in a Virtualization.framework VM. Something lean (no UI, no daemons), zero-config, and Apple Silicon only. I got that running, but I wanted to also use bridge networking and USB device pass-through which require the com.apple.vm.networking and com.apple.developer.accessory-access.usb entitlements, respectively. I was unable to use those for local development using ad-hoc signing, so I guess it requires a paid Apple Developer account and official approval so that they can be enabled in provisioning profiles. I'm open to reactivating my developer subscription which I let expire years ago, but wanted to first assess the chances of getting approval (no point in renewing the subscription if I won't get the permission in the end). I could make this an open source project, if it helps.

I’m building a sandboxed macOS App Store app that registers an agent using SMAppService. I’m trying to understand the IPC setup between the main app and the SMAppService-managed agent. The obvious options seem to be: XPC with a Mach service But from what I understand, I’d need a special entitlement that allows me to communicate over XPC Mach service - which is unlikely to pass Mac App Store review. So how do people communicate with processes registered with SMAppService?

We operate a captive portal WIFI network in a walled-garden setup. There is no public internet access on this network. Users connect to our SSID and can only reach a local resource. On Android, our captive portal can show a button that launches the devices default browser and navigates to our portal page. We cannot reproduce this on iOS: we can place the button inside the CNA tear sheet but tapping it does not open Safari, the redirect simply does not happen. I found this older thread describing the same need: https://developer.apple.com/forums/thread/75498 From that thread, it seems the behavior changed several times. It reportedly worked around iOS 11.2 then broke again in later releases. My questions: On current iOS, is it possible to open Safarı or the default browser programmatically from within the CNA? For example, via a link or button after authentication? If yes, what is the supported way? If it is not supported, is that intentional? Is there any official documentation describing CNA limitations and the recommended pattern? For a walled-garden network with no public Internet, what is Apple's recommended approach to move the user from the CNA into a full browser session?

Apple Mail compose field becomes uneditable after using Apple Intelligence rewriting tools on macOS 27 Developer Beta 1 I am seeing a reproducible issue in Apple Mail on macOS 27 Developer Beta 1 where the compose body becomes locked/uneditable after using Apple Intelligence writing tools. Environment Mac: macOS: macOS 27.0 Developer Beta 1 Build: 26A5353q Device: MacBook Pro with Apple Silicon shouldSwitchToCampoMode: false (isEnhancedSiriAvailable=false) App: Apple Mail Compose window Apple Intelligence Writing Tools Summary When composing an email in Apple Mail, if I write some text and then use Apple Intelligence to rewrite it — for example using Friendly, Professional, or Concise — Mail replaces the original text with the rewritten version. After the rewritten text is inserted, the message body becomes unresponsive. I cannot continue typing, edit the rewritten text, delete text, select text normally, or add new content inside the email body. The Apple Intelligence button also becomes unresponsive after this happens. The only actions that still seem to work are sending the email, discarding the draft, or using some toolbar actions such as emoji insertion. Steps to Reproduce Open Apple Mail on macOS 27 Developer Beta 1. Create a new email. Type any text into the email body. Use Apple Intelligence Writing Tools. Choose a rewrite option such as: Friendly Professional Concise Let Apple Intelligence replace/update the email body text. Try to click back into the message body and continue typing or editing. Expected Result After Apple Intelligence rewrites the email body, the compose field should remain fully editable. The user should be able to: Continue typing after the rewritten text Edit or delete the rewritten text Select and modify text Use Apple Intelligence again on the updated content Continue composing the email normally Actual Result After Apple Intelligence inserts the rewritten text: The email body becomes uneditable. Typing no longer works inside the message body. Clicking inside the body does not restore normal editing. Existing text cannot be edited or changed. Apple Intelligence controls become unresponsive. The compose window itself does not fully crash, but the body editor appears stuck. Send and discard still appear to work. Reproducibility This appears to be reproducible after using Apple Intelligence rewriting tools inside Apple Mail’s compose window. It was working before, so this appears to be a regression in macOS 27 Developer Beta 1.

Hello everyone, I have developed an app that is a local networking monitor app for a specific building automation protocol. I have searched the forum and I think I have found some older posts regarding this topic but I could not figure out if my issue falls under the same category. So my app allows the user to connect to local protocol devices, and start a monitor session where they can see incoming/outgoing packets. The connections are UDP or TCP and require opening a socket. Currently, backgrounding the app will make the OS terminate the socket connection, therefore ending the monitor, even if the app is backgrounded by user, to let's say, perform some other task in their phone. I have several requests from users to improve the app by allowing the monitor to continue while the app is backgrounded. However, by reading the relevant documents, I have found this to be almost impossible in iOS app. I have considered: Remote Push Notifications (APNs): The app operates on LAN so this is not an option, since I do not have an infrastructure to somehow send notifications to keep app process alive. Background Tasks (BGTaskScheduler): Not my case, since I do not want periodic execution. The app requires continuous socket listening. VoIP, VPN, or Audio Background Modes: My app does not fall under any of these categories, even though this would solve my situation. By searching around a bit more, I might be able to use either BGProcessingTask, which would allow my app at least to run for some minutes and show the user that they have to foreground it in order to not stop the monitor process, or maybe even App Intents framework. Has anyone faced similar requirement for their app? Any tip or point to a direction I should investigate more? Thanks, Nikos

I am seeing serious issues with iPhone Mirroring on macOS 27 Developer Beta 1. Environment Mac: MacBook Pro, Apple M4 Pro Model: Mac16,7 RAM: 24 GB macOS: macOS 27.0 Developer Beta 1 Build: 26A5353q SIP: Enabled Developer Mode: Enabled iPhone: iPhone 15 Pro Max Previously tested on: iOS 27 Beta 1 Currently restored to: iOS 26.5 Issue 1: iPhone Mirroring does not connect on iOS 27 Beta 1 and can leave the iPhone unusable When my iPhone 15 Pro Max was running iOS 27 Beta 1, iPhone Mirroring on macOS 27 Developer Beta 1 did not connect properly. I tried connecting multiple times. The iPhone appeared to think that the mirroring session had started successfully, because the iPhone screen turned off as expected for iPhone Mirroring. However, the Mac never actually completed the connection and never displayed the mirrored iPhone session. After this happened, the iPhone became completely stuck and unresponsive. The phone did not respond normally, and even force restart attempts were not working. The device remained unusable until the battery fully drained, which took about two days. After the battery was fully depleted, I was able to put the iPhone into DFU mode and restore it back to iOS 26.5. This suggests that something may be broken in the iPhone Mirroring / Continuity connection state between macOS 27 Developer Beta 1 and iOS 27 Beta 1. The iPhone seems to enter a state where it believes it is connected for mirroring, while the Mac never actually establishes the session. Issue 2: iPhone Mirroring crashes on macOS 27 Developer Beta 1 when used with iOS 26.5 After restoring the iPhone 15 Pro Max back to iOS 26.5, I was able to get a crash report from the Mac side. The iPhone Mirroring app crashed on macOS 27 Developer Beta 1 with the following details: Process: iPhone Mirroring Identifier: com.apple.ScreenContinuity Version: 2.0 Build Version: 114.38.15.1 OS Version: macOS 27.0 (26A5353q) Hardware Model: Mac16,7 Exception Type: EXC_BREAKPOINT (SIGTRAP) Termination Reason: Namespace SIGNAL, Code 5, Trace/BPT trap: 5 Triggered by Thread: 2 Dispatch Queue: com.apple.root.user-initiated-qos.cooperative The crashed thread shows a Swift assertion failure inside ScreenSharingKit.framework: Thread 2 Crashed: 0 libswiftCore.dylib assertionFailure(:_:file:line:flags:) + 216 1 ScreenSharingKit 0x29fbb60e0 2 libswiftCore.dylib _swift_release_dealloc + 64 3 libswiftCore.dylib RefCounts::doDecrementSlow 4 ScreenSharingKit 0x29fa894c0 5 ScreenSharingKit 0x29fb484d8 6 ScreenSharingKit 0x29fb48614 ... 15 libswift_Concurrency.dylib completeTaskWithClosure Relevant binary image: /System/Library/PrivateFrameworks/ScreenSharingKit.framework/Versions/A/ScreenSharingKit CFBundleIdentifier: com.apple.screensharing.ScreenSharingKit CFBundleVersion: 114.38.15.1 Crash interpretation The crash appears to be a first-party Apple framework crash inside ScreenSharingKit, caused by a Swift assertion failure. It does not appear to be caused by memory pressure, Rosetta, or third-party code injection. Relevant crash report details: External Modification Summary: task_for_pid: 0 thread_create: 0 thread_set_state: 0 System Integrity Protection: enabled Memory usage also does not look excessive: Writable regions: Total=251.0M MALLOC: 128.4M Expected behavior iPhone Mirroring should either connect successfully or fail gracefully. It should not: Leave the iPhone in a stuck/unresponsive state. Put the iPhone screen into mirroring mode while the Mac never completes the connection. Require the iPhone battery to fully drain before DFU restore is possible. Crash on macOS with an internal ScreenSharingKit Swift assertion failure. Actual behavior On iOS 27 Beta 1: iPhone Mirroring never completed the connection on the Mac. The iPhone behaved as if the session started. The iPhone screen turned off. The iPhone became completely unresponsive. Force restart did not work. Device only became recoverable after battery fully drained. I then restored the iPhone to iOS 26.5 via DFU. On iOS 26.5: iPhone Mirroring was able to run, but the Mac-side app later crashed. The crash occurred inside Apple’s ScreenSharingKit.framework. The crash type was EXC_BREAKPOINT (SIGTRAP) from Swift _assertionFailure. Reproducibility Partially reproducible. iOS 27 Beta 1 + macOS 27 Developer Beta 1: connection repeatedly failed and eventually left the iPhone stuck. iOS 26.5 + macOS 27 Developer Beta 1: iPhone Mirroring can connect, but the Mac app crashed with the attached report. Crash identifiers Incident Identifier: B6D4D86D-03C4-4466-B9D6-4CF70DF0B46F Crash Reporter Key: 8BD85D40-8AC8-E771-2D80-153D7C4C5366 Process: iPhone Mirroring [11429] Bundle ID: com.apple.ScreenContinuity The crash report points to ScreenSharingKit.framework, so this looks like a possible beta regression in the iPhone Mirroring / Continuity stack.

The on-demand economy has transformed how businesses operate, and fuel delivery services are no exception. From mobile fueling for commercial fleets to doorstep fuel delivery for consumers, companies are investing heavily in advanced mobile applications to streamline operations, improve customer experiences, and optimize logistics. New York City is home to several leading app development firms that specialize in building innovative fuel delivery platforms. These companies offer expertise in mobile app development, route optimization, GPS tracking, payment integrations, fleet management, and real-time analytics. Choosing the right development partner can significantly impact the success of your fuel delivery business. This guide highlights the best fuel delivery app development companies in NYC, their strengths, key services, and reasons they stand out in the competitive app development market. 1. Suffescom Solutions Suffescom Solutions is a renowned mobile app development company offering custom on-demand fuel delivery solutions. Their team develops scalable applications equipped with real-time tracking, secure payments, and fleet management capabilities. Why They’re Selected Extensive experience in on-demand app development Expertise in fuel delivery and logistics platforms Strong portfolio across multiple industries Scalable and secure application architecture End-to-end development and maintenance support Key Services Fuel delivery app development Fleet management solutions GPS tracking integration Payment gateway integration UI/UX design App maintenance and support 2. BitsWits BitsWits specializes in creating innovative mobile applications for startups and enterprises. Their fuel delivery solutions emphasize user-friendly interfaces, automation, and advanced operational management features. Why They’re Selected Strong mobile-first development approach Custom-built applications tailored to business needs Agile development methodology Focus on performance and scalability Experienced development team Key Services Custom app development Fuel delivery application development Android and iOS app development Backend development API integrations Quality assurance testing 3. Fueled Fueled is a well-established digital product agency known for developing premium mobile applications. The company delivers high-performing fuel delivery platforms with intuitive customer experiences and advanced functionality. Why They’re Selected Strong reputation in mobile app development Expertise in enterprise-grade applications Innovative design capabilities Proven project delivery record Focus on user engagement Key Services Mobile app development Product strategy UX/UI design Backend engineering Cloud integration Digital transformation solutions 4. FuGenX Technologies FuGenX Technologies provides comprehensive app development services for businesses seeking digital transformation. Their fuel delivery solutions incorporate advanced technologies to improve operational efficiency and customer convenience. Why They’re Selected Global experience across industries Skilled development professionals Advanced technology adoption Cost-effective development solutions Strong support services Key Services Fuel delivery app development Enterprise mobility solutions Cross-platform app development AI-powered integrations Cloud solutions Maintenance and upgrades 5. Nectarbits Nectarbits delivers innovative mobile and web applications designed for on-demand service industries. Their expertise helps fuel delivery businesses streamline logistics and improve customer satisfaction. Why They’re Selected Specialized in on-demand applications Strong technical expertise Customized development approach Reliable project management Excellent customer support Key Services Mobile app development Fuel delivery platform development Fleet tracking systems Web application development API development Technical consulting 6. Apps Chopper Apps Chopper focuses on building custom mobile applications that help businesses achieve operational excellence. Their fuel delivery solutions support seamless fuel ordering and real-time service management. Why They’re Selected Extensive mobile development expertise User-focused design philosophy Strong development framework Transparent project execution Reliable post-launch support Key Services iOS app development Android app development Fuel delivery app solutions UI/UX design App testing App modernization services 7. Hyperlocal Cloud Hyperlocal Cloud is recognized for developing hyperlocal and on-demand delivery solutions. The company offers feature-rich fuel delivery applications that enable businesses to manage operations efficiently. Why They’re Selected Specialization in hyperlocal delivery models Advanced logistics management expertise Quick deployment capabilities Scalable application infrastructure Industry-focused development approach Key Services Hyperlocal app development Fuel delivery platform development Route optimization solutions Real-time tracking integration Dispatch management systems Cloud-based solutions 8. Konstant Infosolutions Konstant Infosolutions is a leading app development company serving startups and enterprises worldwide. Their fuel delivery solutions combine innovative technology with scalable business-focused functionality. Why They’re Selected Over a decade of development experience Strong international client base Comprehensive development services Flexible engagement models Proven success across industries Key Services Mobile application development Fuel Delivery App Development Company solutions Cross-platform development Cloud integration Enterprise software development Ongoing support and maintenance Conclusion The demand for on-demand fuel delivery services continues to rise as businesses and consumers seek greater convenience and efficiency. Partnering with an experienced app development company can help you build a reliable, scalable, and feature-rich platform that meets market expectations. The companies listed above have demonstrated expertise in developing advanced mobile applications and on-demand solutions. By carefully evaluating your business requirements and development goals, you can select the right technology partner to bring your fuel delivery app vision to life.

Hey guys, can everyone share how long an estimated time range it took to get the new siri AI

Overview Using NotificationCenter's messages NSPersistentCloudKitContainer.EventChangedMessage (AsyncMessage) causes crash When the this project is run on iOS 27 simulator, app crashes Environment macOS: 26.5.1 (25F80) Xcode: Version 27.0 beta (27A5194q) Simulator: iPhone 17 Pro Simulator OS: iOS 27 Code causing the crash: let messages = NotificationCenter.default.messages( of: NSPersistentCloudKitContainer.self, for: .eventChanged ) Looks like the symbol is not even present Feedback: FB23220378 Logs dyld[31078]: Symbol not found: _$sSo29NSPersistentCloudKitContainerC8CoreDataE19EventChangedMessageVSo20NSNotificationCenterC10FoundationE05AsyncI0ACMc Referenced from: <488D9AA6-ED4C-3189-9A08-044D576D498D> /Users/username/Library/Developer/CoreSimulator/Devices/331ADE41-8F3A-4EBE-9E3B-B335B29224D3/data/Containers/Bundle/Application/573DF3FC-E202-4D47-A85F-E5D4D1421EAC/NotificationMessageDemo.app/NotificationMessageDemo.debug.dylib Expected in: <483D9879-24DB-3695-AFE5-B14E2D673F36> /private/var/run/com.apple.security.cryptexd/mnt/com.apple.iPhoneOS.SimulatorRuntime-v24.1.5355.16.mnzElK/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 27.0.simruntime/Contents/Resources/RuntimeRoot/System/Library/Frameworks/CoreData.framework/CoreData Symbol not found: _$sSo29NSPersistentCloudKitContainerC8CoreDataE19EventChangedMessageVSo20NSNotificationCenterC10FoundationE05AsyncI0ACMc Referenced from: <488D9AA6-ED4C-3189-9A08-044D576D498D> /Users/username/Library/Developer/CoreSimulator/Devices/331ADE41-8F3A-4EBE-9E3B-B335B29224D3/data/Containers/Bundle/Application/573DF3FC-E202-4D47-A85F-E5D4D1421EAC/NotificationMessageDemo.app/NotificationMessageDemo.debug.dylib Expected in: <483D9879-24DB-3695-AFE5-B14E2D673F36> /private/var/run/com.apple.security.cryptexd/mnt/com.apple.iPhoneOS.SimulatorRuntime-v24.1.5355.16.mnzElK/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 27.0.simruntime/Contents/Resources/RuntimeRoot/System/Library/Frameworks/CoreData.framework/CoreData dyld config: DYLD_SHARED_CACHE_DIR=/Library/Developer/CoreSimulator/Caches/dyld/25F80/com.apple.CoreSimulator.SimRuntime.iOS-27-0.24A5355p/ DYLD_ROOT_PATH=/private/var/run/com.apple.security.cryptexd/mnt/com.apple.iPhoneOS.SimulatorRuntime-v24.1.5355.16.mnzElK/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 27.0.simruntime/Contents/Resources/RuntimeRoot DYLD_LIBRARY_PATH=/Users/username/Library/Developer/Xcode/DerivedData/NotificationMessageDemo-gungjtytarzeijdspglltylscocj/Build/Products/Debug-iphonesimulator DYLD_INSERT_LIBRARIES=/private/var/run/com.apple.security.cryptexd/mnt/com.apple.iPhoneOS.SimulatorRuntime-v24.1.5355.16.mnzElK/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 27.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/libLogRedirect.dylib:/private/var/run/com.apple.security.cryptexd/mnt/com.apple.iPhoneOS.SimulatorRuntime-v24.1.5355.16.mnzElK/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 27.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/libMainThreadChecker.dylib:/usr/lib/libRPAC.dylib:/private/var/run/com.apple.security.cryptexd/mnt/com.apple.iPhoneOS.SimulatorRuntime-v24.1.5355.16.mnzElK/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 27.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/libViewDebuggerSupport.dylib DYLD_FRAMEWORK_PATH=/Users/username/Library/Developer/Xcode/DerivedData/NotificationMessageDemo-gungjtytarzeijdspglltylscocj/Build/Products/Debug-iphonesimulator DYLD_FALLBACK_FRAMEWORK_PATH=/private/var/run/com.apple.security.cryptexd/mnt/com.apple.iPhoneOS.SimulatorRuntime-v24.1.5355.16.mnzElK/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 27.0.simruntime/Contents/Resources/RuntimeRoot/System/Library/Frameworks DYLD_FALLBACK_LIBRARY_PATH=/private/var/run/com.apple.security.cryptexd/mnt/com.apple.iPhoneOS.SimulatorRuntime-v24.1.5355.16.mnzElK/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 27.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib Debug session ended with code 9: killed

Hello, I am exploring an iPadOS product idea for Apple Pencil users and would like to understand the current public API boundary. The user need is a temporary, user-controlled Apple Pencil annotation layer while the user is working in another app or workspace. For example, a student may be reading in Books, Safari, a PDF app, or another educational app and want to write quick Pencil notes directly over the visible material without taking a screenshot or exporting the content first. I understand that PencilKit works inside an app's own UI, and I also understand that iPadOS sandboxing prevents third-party apps from inspecting or modifying other apps. I am not trying to bypass that model. What I am trying to determine is: Is there any current public API, extension point, or entitlement that allows a user-initiated Apple Pencil overlay session across the current iPadOS workspace? If not, is Feedback Assistant the right place to request a new PencilKit / iPadOS entitlement for this use case? Are there existing Apple-recommended patterns for this workflow beyond Quick Note, Screenshot Markup, Split View, Stage Manager, or importing content into the developer's own app? The privacy model I have in mind would be strict: The overlay is user initiated only. A visible system indicator is shown while active. The developer app receives Pencil stroke data only by default. The app cannot inspect the underlying app's view hierarchy, documents, text, or private data. Screen pixels are not captured unless the user grants separate explicit permission. The user can close or clear the overlay at any time. The closest mental model is a system-mediated Pencil annotation layer, not a background screen recorder or a way to control another app. If this is not possible today with public APIs, I would appreciate confirmation so I can file a clear enhancement request through Feedback Assistant. I also filed this as Feedback Assistant report FB23067750. Thank you.

I previously attempted to apply for the hotspot-provider entitlement but was rejected. I no longer require this entitlement. I need to remove the hotspot-provider permission although the Network Extensions capability is checked. However, the generated provisioning profile still includes the hotspot-provider permission, which causes error 409 when I upload the IPA file. I only need the Network Extensions entitlement. Could you please advise how to remove hotspot-provider from the provisioning profile?