If you need help investigating a crash, please include a crash report in your post. To smooth things along, follow these guidelines: For information on how to get a crash report, see Acquiring crash reports and diagnostic logs. Include the whole crash report as a text attachment (click the paperclip icon and then choose Add File). This avoids clogging up the timeline while also preserving the wealth of information in the crash report. If you’re not able to post your crash report as an attachment, see Can’t Post Crash Report as Attachment below. If you want to highlight a section of the report, include it in the main body of your post. Put the snippet in a code block so that it renders nicely. To create a code block, add a delimiter line containing triple backquotes before and after the block, or just click the Code Block button. If possible, post an Apple crash report. Third-party crash reporters are often missing critical information and have general reliability problems (for an explanation as to why, see Implementing Your Own Crash Reporter). Symbolicate your crash report before posting it. For information on how to do this, see Adding identifiable symbol names to a crash report. If you need to redact the crash report, do so consistently. Imagine you’re building the WaffleVarnish app whose bundle ID is com.example.wafflevarnish but you want to keep your new waffle varnishing technology secret. Replace WaffleVarnish with WwwwwwVvvvvvv and com.example.wafflevarnish with com.eeeeeee.wwwwwwvvvvvvv. This keeps the text in the crash report aligned while making it possible to distinguish the human-readible name of the app (WaffleVarnish) from the bundle ID (com.example.wafflevarnish). Finally, for information on how to use a crash report to debug your own problems, see Diagnosing issues using crash reports and device logs. Can’t Post Crash Report as Attachment Crash reports have two common extensions: .crash and .ips. If you have an .ips file, please post that [1]. DevForums lets you attach a .crash file but not an .ips file (r. 117468172). To work around this, change the extension to .txt. If DevForums complains that your crash report “contains sensitive language”, leave it out of your initial post and attach it to a reply. That often avoids this roadblock. If you still can’t post your crash report, upload it to a file sharing service and include the URL in your post. Post the URL in the clear, per tip 14 in Quinn’s Top Ten DevForums Tips. Getting a Crash Report from the Xcode Organiser The Xcode organiser shows crash reports from customers. If you’re investigating such a crash and want to post a crash report: Navigate to the crash in the Xcode organiser. Note If you can’t see the right crash, check the filter popups at the top. In the list of crashes, secondary click on your crash and choose Show in Finder. That reveals the Xcode crashpoint document (.xccrashpoint) in the Finder. Secondary click on that and choose Show Package Contents. In the resulting Finder window, find a crash report (.crash) that accurately represents the crash you’re investigating and attach that to your forums post. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = "eskimo" + "1" + "@" + "apple.com" [1] Because it’s easy to go from an .ips file to a .crash file. I usually do this by choosing File > Quick Look in the Finder. For more info about these file formats, see this post. Revision History: 2025-08-29 Added the Getting a Crash Report from the Xcode Organiser section. 2024-11-21 Added a recommendation to post the .ips format if possible. 2024-05-21 Added some advice regarding the “contains sensitive language” message. 2023-10-25 Added the Can’t Post Crash Report as Attachment section. Made other minor editorial changes. 2021-08-26 First posted.

General: DevForums tags: Debugging, LLDB, Graphical Debugger Xcode > Debugging documentation Diagnosing memory, thread, and crash issues early documentation Diagnosing issues using crash reports and device logs documentation Choosing a Network Debugging Tool documentation Testing a release build documentation Isolating Code Signing Problems from Build Problems DevForums post What is an exception? DevForums post Language Exception from RCTFatal DevForums post Standard Memory Debugging Tools DevForums post Using a Sysdiagnose Log to Debug a Hard-to-Reproduce Problem DevForums post Posting a Crash Report DevForums post Creating a test project DevForums post Implementing Your Own Crash Reporter DevForums post Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = "eskimo" + "1" + "@" + "apple.com"

Hi, I’m encountering an issue when profiling an application with xctrace and Instruments on macOS. When I try to record a trace using either the CPU Profiler or CPU Counters template, the recording fails with the following error: Failed to start the recording: configureHardwareCounters: Failed set kpc configuration: Operation not permitted. The issue was also present in the previous macOS 27.0 build (26A428) and remains after updating to macOS 27.0.1 (26A434) System: Apple M6 Mac mini macOS 27.0.1, build 26A434 Xcode 27.0, build 27A266a

Since iOS 27.2 (24B119), SwiftData no longer sets the inverse (child → parent) relationship for the children of a model that hasn't been inserted yet when that model is attached to an already-saved model. The children are saved with a nil parent, so the parent's to-many relationship reads back empty. This happens in the same ModelContext and also after reopening the store. The same code works correctly on iOS 27.0 (24A5390f). @Model final class Ledger { @Relationship(deleteRule: .cascade, inverse: \Transaction.ledger) var transactions: [Transaction] = [] } @Model final class Transaction { var ledger: Ledger? @Relationship(deleteRule: .cascade, inverse: \Item.transaction) var items: [Item] = [] init(items: [Item]) { self.items = items } } @Model final class Item { var transaction: Transaction? } // Inside a @ModelActor; `ledger` is fetched and already saved. let transaction = Transaction(items: [Item(), Item()]) // not inserted ledger.transactions.append(transaction) // iOS 27.0: item.transaction === transaction for every item // iOS 27.2: item.transaction == nil for every item try modelContext.save() // iOS 27.2: transaction.items.count == 0 (expected 2); both items are orphaned rowsThe inverse is already nil before save(), so this isn't a save or flush problem. The link just isn't set when the graph is attached. Affected patterns on 27.2 • persisted.list.append(uninsertedParentWithChildren) • persisted.list[index] = uninsertedParentWithChildren • Reassigning persisted.list = [...] when the new models have their own child arrays (grandchildren end up orphaned) • Models with several to-many arrays of the same child type Not affected • A graph that's entirely new, including the root • To-one relationships set in init • Models inserted into the context before the relationship is set Toolchain ruled out. I built the repro on the same iPhone 13 (iOS 27.2) with three toolchains: xcode 26.6, 27.1 and 27.2 Workaround. Insert the children and set the inverse explicitly before saving: modelContext.insert(transaction) for item in transaction.items { modelContext.insert(item) item.transaction = transaction } ledger.transactions.append(transaction) try modelContext.save()You have to do this at every level, grandchildren included. Has anyone else seen this on 27.2? And can someone from the SwiftData team confirm whether this is an intended behavior change or a regression? Feedback: FB25355425 (includes a standalone repro project, reports from iOS 27.0 and 27.2, and a sysdiagnose)

I am investigating a startup failure when running Node.js under a restrictive sandbox-exec profile. I would appreciate guidance on diagnosing the failure and on a supported way to run a command-line process with restricted filesystem access and no network access. I have not established whether this is caused by my profile, the operating system, or another interaction. Environment macOS 26.6.2, build 25G83 Apple silicon, ARM64, without Rosetta Official Node.js 22.23.4 darwin-arm64 distribution; its archive SHA-256 matches the published checksum Python 3.14 launching the process from Terminal No sudo, application code, third-party JavaScript modules, credentials, or real user data The Node version above identifies the downloaded distribution. I have not confirmed a successful node --version execution in this restricted environment. Launch configuration The invocation has this form: /usr/bin/sandbox-exec -f <PROFILE> <NODE> -e <JS> <INPUT> <WORK>Python uses subprocess.Popen, with: Working directory set to <WORK> start_new_session=True Standard output and error captured through pipes A 10-second execution deadline and a 6-second termination/cleanup allowance Only these environment variables are supplied; the parent environment is not inherited: PATH=<NODE_DIR>:/usr/bin:/bin HOME=<WORK> TMPDIR=<WORK>NODE_OPTIONS and DYLD_* are not set. The JavaScript starts with: console.log("NODE_JS_ENTRY");It then uses node:fs to read a synthetic input and write markers in the permitted work directory. The initial console marker is never observed. Filesystem and network restrictions The profile uses (deny default) and (deny network*). It permits process creation, execution of the specified Node binary, and sysctl-read. File reads are allowed for the Node binary, synthetic input/work directories, /System/Library, /usr/lib, and the specific devices /dev/null, /dev/random, and /dev/urandom. Ancestor-directory metadata access is listed using individual literal paths. Writes are allowed only inside the work directory. The Node binary and synthetic fixtures are in separate dedicated directories under the user's Documents directory. This is a description of the profile, not a complete runnable reproduction. Paths are anonymized here. I tested two additional permission variants: A — ancestor metadata and existence checks: (allow file-read-metadata file-test-existence (literal "/System/Volumes") (literal "/System/Volumes/Preboot"))A+B — the above plus Cryptexes reads and executable mapping: (allow file-read* file-map-executable file-test-existence (subpath "/System/Volumes/Preboot/Cryptexes"))Neither variant resolved the startup failure. No general Mach/IPC permissions, broad /etc read access, localhost access, or system.sb import were added. Observed results The original profile and both variants terminated with SIGABRT, without the initial JavaScript marker. For A and A+B: Python reported child return code -6. Standard output and error were both empty. The parent sent no termination signal; these were not timeout terminations. The direct child was reaped, and its process group was no longer present. For two earlier executions using the original profile, I matched saved crash reports to the process and Node binary image. They showed: Exception: EXC_CRASH / SIGABRT Termination namespace: 0x23 Termination code: 2 Termination flags: 582The stack included: __abort_with_payload abort_with_payload_wrapper_internal abort_with_reason ignition_halt boot_boot ignite dyld4::CacheFinder::CacheFinder dyld4::ProcessConfig::DyldCache::DyldCache dyld4::ProcessConfig::ProcessConfig dyld4::start startApple's public XNU definitions identify namespace 35 as OS_REASON_LIBIGNITION. I have not established the meaning of code 2 for this OS build. I have not inspected matching crash stacks for A or A+B, so I cannot claim they stopped at the same internal location. Questions Is sandbox-exec a supported mechanism for this use case on this macOS version? If not, what supported approach can enforce both restricted filesystem access and no network access for a command-line process and its children? What diagnostic information would distinguish a missing sandbox permission from a loader/cache initialization problem? Does this termination signature suggest a documented diagnostic procedure or known issue? My goal is to reach JavaScript execution while preserving the restrictions, rather than broadly allowing filesystem access or network communication. I can provide a sanitized profile and relevant diagnostic excerpts if needed. Thank you. Correction and update after checking the saved crash reports: The original-profile runs were on macOS 26.6.2 (25G83), while the A and A+B runs were on macOS 26.7.2 (25G332). My initial post did not distinguish these environments correctly. The saved reports for A and A+B have now been matched to the recorded execution times, process IDs, and Node image information. Both show SIGABRT, termination namespace 0x23, code 2, and the same 11-frame sequence of function names and offsets as the original-profile reports, including ignite, boot_boot, and ignition_halt. The Node image UUID is unchanged, but the OS version and dyld image identifiers differ. These results therefore must not be treated as a controlled comparison in which only the sandbox profile changed. The matching termination signatures do not establish an identical root cause. The specific reason for LIBIGNITION code 2 remains unknown. No additional executions or permission changes have been performed.

Each time I launch a Debug version of the app on iOS Simulator, I see the Launch Screen presented and then about a 30-second delay before the app is responsive and debug output appears in the console panel. Filed FB22345091

My app keeps crasheing 30 seconds after launch on a particular ipad only, I have no idea what the problem is, need some help on debugging please.

A restricted local metadata-only OpenSSL command startup aborted with EXC_CRASH/SIGABRT. A correlated crash report displayed termination namespace0x23, code2. We have not uniquely tied that report to a saved PID/build identity, so attribution remains qualified. The control was an OpenSSL x509 metadata command reading via standard input under a custom deny-default process sandbox denying network and Mach lookups. No signature verification of a provisioning profile ran; we do not know which operation or rule caused the abort. The control did not establish provisioning-profile authenticity. Recorded environment: macOS26.7.1/build25G241; one read-only kern.version query returned Darwin25.6.0 and XNU12377.161.15.700.19~2. We have not assumed those identifiers establish an equivalence to a published source revision. Apple published XNU at commit f6217f891ac0bb64f3d375211650a4c1ff8ca1ea defines OS_REASON_LIBIGNITION35 in bsd/sys/reason.h, but that file does not define LIBIGNITION code2. Could Apple clarify: 1.Is there a documented meaning of LIBIGNITION termination code2 applicable to this runtime, and a supported way to identify its originating failure without relaxing security controls or relying on undocumented namespace guesses? 2.What is the supported Apple procedure for verifying a development provisioning profile and signer policy without modifying global trust/keychain settings? We do not want to substitute an invented OpenSSL purpose/OID policy for Apple's validation. We have made no security-setting changes or signing/build/install retry as part of this inquiry. No certificates, profiles, credentials, account/device identifiers, private paths, raw logs or source code are included. This is a request for documented guidance, not approval to weaken a sandbox. No message has been submitted.

Hi there! I'm pretty new in coding. Right now I'm just vibe coding, trying to understand what happens and how does this works. I made a simple app in Swift Playground on my iPad Mini A17 Pro, and everything works good so far when I tap the Play (Run) button, except text input: every text field only shows the blinking cursor and let me paste, but the virtual keyboard don't appear, and even connecting a physical keyboard has no better outcome. What am I doing wrong? Thanks.

Safari continues to display a "Fraudulent Website Warning" for openvan.camp despite the domain being clean across all major security databases for over a week. Chrome, Firefox, and all other browsers open the site without any warnings. Domain: openvan.camp Warning appeared: March 18, 2026 Warning type: Fraudulent Website Warning (red screen) Current security database status: Google Safe Browsing: ✅ Clean (transparencyreport.google.com) Google Search Console: ✅ No security issues Spamhaus DBL: ✅ Removed from blocklist Fortinet FortiGuard: ✅ Category "Travel" VirusTotal: ✅ 0/65 vendors URLVoid: ✅ 0/35 engines Steps taken: Removed the third-party ad network (Adsterra) that caused the original flag — March 18, 2026 Migrated hosting to Scaleway (AS12876, France), IP: 151.115.84.228 Configured SPF, DKIM, DMARC records Created functional abuse@ and postmaster@ role accounts Submitted review via websitereview.apple.com — no response after 5 days What we believe is happening: Apple's Safe Browsing database appears to have an independent entry for this domain that has not been updated despite all underlying security databases clearing the flag. Safari's warning persists even after deleting ~/Library/Safari/SafeBrowsing/ cache and re-downloading the database — which confirms this is not a local cache issue. Steps to reproduce: Open Safari on macOS or iOS Navigate to https://openvan.camp/ Safari displays "Fraudulent Website Warning" Open the same URL in Chrome — no warning Expected behavior: No warning should be shown. The domain is legitimate, clean, and verified. Has anyone experienced a similar issue? Is there any additional channel to escalate beyond websitereview.apple.com?

Hello, I started writing my app on Xcode 26 and everything worked super smoothly. A build would take less than a minute and would immediately open the app on my iPhone 13 Pro. After updating to XCode 27 a build would still finish in the same amount of time, but it would only open the app maybe once out of 10 attempts, most of the time though nothing happens. No matter how long I wait, if I disconnect, reconnect, unlock my phone, it seems like xcode doesn't even notice. I display the build time inside the app and when I manually open the app I can see that it's from the last time the build successfully launched the app automatically. So it's stuck somewhere between building and loading it onto my phone I assume. I recently updated my phone to an 18 Pro and the issue persists. Connection is via USB-C cable. Anyone have any suggestions what might be wrong? Thank you!

Hello Hivemind! We are facing an issue that I think many people do these days - how to successfully work from home and specifically how to debug an iPhone from a remote location. We are working from home due to COVID 19, we're using VNC to connect to our Mac's at the office. For most needs, we can use that Mac's iOS simulator. However some of our teams are working on Network Extension to develop VPN which is not supported by the simulator. We are looking for a solution to enable them to work efficiently. There can be 2 options: Debug over the internet - use a local iPhone so we can control it manually, and be able to connect to it with the remote Mac (the one in the office) that is running Xcode and debugging. Have the device connected to the remote mac, and be able to control it remotely. This option should be direct control via that Mac's USB, because since we are developing a VPN product - we sometimes have network issues during debug. The solution should be - Fast enough to allow debugging of networking issues (UI waits on you, but servers don't. So we need to be able to make flows that won't break if debugger is slow). Reliable enough so we don't need to have "some guy in the office". Any suggestion will be most appreciated, thanks!

Hi, I understand Scenekit is deprecated in ios27, but expectation is that it should continue working in ios27 and not anymore maintained. With ios27 , when we attempt to set self.delegate in an ARSCNViewDelegate we receive a crash. Is there any workaround to have that fixed until we have time to move away from Scenekit? Can this be part of a fix in ios27 considering we should have sometime to migrate out production apps or that won't go through? Thank you.

Starting with Xcode 27, my attempt to start a debug session for my C++ project fails. The Run scheme used has the Console setting configured for "Terminal" fails. The Terminal opens, but there appears to be a failure in the execution of the 'darwin-debug' command in the shell spawned for the debug session: Here's the output in the Terminal: Last login: Sat Sep 19 13:46:54 on ttys001 /bin/bash -c 'arch -arch arm64 "/Volumes/MyPassport/Applications/Xcode.app/Contents/SharedFrameworks/LLDB.framework/Resources/darwin-debug" --unix-socket=/tmp/7RBHab --arch=arm64 --working-dir "/Volumes/MyPassport/paulrockwell/Library/Developer/Xcode/DerivedData/GNU_APL-gulwhsgobkphkodqgsftvqohegyk/Build/Products/Debug" --disable-aslr --env="OS_ACTIVITY_TOOLS_PRIVACY=YES" --env="OS_LOG_DT_HOOK_PREFIX=OSLOG-E37B26CB-6471-4B1C-ACB7-48236B4EC921" --env="TERM=dumb" --env="SHELL=/bin/zsh" --env="MTL_DEBUG_LAYER_VALIDATE_STORE_ACTIONS=0" --env="DYLD_FRAMEWORK_PATH=/Volumes/MyPassport/paulrockwell/Library/Developer/Xcode/DerivedData/GNU_APL-gulwhsgobkphkodqgsftvqohegyk/Build/Products/Debug" --env="SWIFT_BACKTRACE=enable=no" --env="CA_ASSERT_MAIN_THREAD_TRANSACTIONS=0" --env="CFLOG_FORCE_DISABLE_STDERR=1" --env="__XCODE_BUILT_PRODUCTS_DIR_PATHS=/Volumes/MyPassport/paulrockwell/Library/Developer/Xcode/DerivedData/GNU_APL-gulwhsgobkphkodqgsftvqohegyk/Build/Products/Debug" --env="IDE_DISABLED_OS_ACTIVITY_DT_MODE=1" --en% paulrockwell@Upstairs ~ % /bin/bash -c 'arch -arch arm64 "/Volumes/MyPassport/Applications/Xcode.app/Contents/SharedFrameworks/LLDB.framework/Resources/darwin-debug" --unix-socket=/tmp/7RBHab --arch=arm64 --working-dir "/Volumes/MyPassport/paulrockwell/Library/Developer/Xcode/DerivedData/GNU_APL-gulwhsgobkphkodqgsftvqohegyk/Build/Products/Debug" --disable-aslr --env="OS_ACTIVITY_TOOLS_PRIVACY=YES" --env="OS_LOG_DT_HOOK_PREFIX=OSLOG-E37B26CB-6471-4B1C-ACB7-48236B4EC921" --env="TERM=dumb" --env="SHELL=/bin/zsh" --env="MTL_DEBUG_LAYER_VALIDATE_STORE_ACTIONS=0" --env="DYLD_FRAMEWORK_PATH=/Volumes/MyPassport/paulrockwell/Library/Developer/Xcode/DerivedData/GNU_APL-gulwhsgobkphkodqgsftvqohegyk/Build/Products/Debug" --env="SWIFT_BACKTRACE=enable=no" --env="CA_ASSERT_MAIN_THREAD_TRANSACTIONS=0" --env="CFLOG_FORCE_DISABLE_STDERR=1" --env="__XCODE_BUILT_PRODUCTS_DIR_PATHS=/Volumes/MyPassport/paulrockwell/Library/Developer/Xcode/DerivedData/GNU_APL-gulwhsgobkphkodqgsftvqohegyk/Build/Products/Debug" --env="IDE_DISABLED_OS_ACTIVITY_DT_MODE=1" --en There appears to be a missing single quote in the command line, but if I complete it, darwin-debug fails to start with the following error message: darwin-debug: option `--en' requires an argument This worked on Xcode 26. Any thoughts on what might have changed and can I update the project to get around this? This issue is happening on any C++ project that I've created on prior versions of Xcode. And yes, I need to debug operation of one of the projects using the Terminal - the one project I'm interested in is GNU APL, which makes heavy use of terminfo and alternate character sets in its operation.

Since the beta releases of iPadOS 26 we have been having some crashes about Invalid parameter not satisfying: parentEnvironment != nil We got to contact a couple of users and we found out that the crash appears when entering a screen in a UINavigationController with the iPad device connected to a Magic Keyboard. If the device is not connected to the keyboard then nothing happens and everything works ok. From our end we haven't managed to reproduce the crash so I am pasting part of the stacktrace if it can be of any help. 3 UIKitCore 0x19dfd2e14 -[_UIFocusContainerGuideFallbackItemsContainer initWithParentEnvironment:childItems:] + 224 (_UIFocusContainerGuideFallbackItemsContainer.m:23) 4 UIKitCore 0x19dae3108 -[_UIFocusContainerGuideImpl _searchForFocusRegionsInContext:] + 368 (_UIFocusGuideImpl.m:246) 5 UIKitCore 0x19db28498 -[_UIFocusMapSnapshot addRegionsInContainer:] + 2720 (_UIFocusMapSnapshot.m:531) 6 UIKitCore 0x19db28900 -[_UIFocusMapSnapshot addRegionsInContainers:] + 160 (_UIFocusMapSnapshot.m:545) 7 UIKitCore 0x19d1313dc _UIFocusRegionSearchContextSearchForFocusRegionsInEnvironment + 632 (_UIFocusRegion.m:143) 8 UIKitCore 0x19db1d244 -[_UIFocusRegionContainerProxy _searchForFocusRegionsInContext:] + 140 (_UIFocusRegionContainerProxy.m:184) 9 UIKitCore 0x19db28498 -[_UIFocusMapSnapshot addRegionsInContainer:] + 2720 (_UIFocusMapSnapshot.m:531) 10 UIKitCore 0x19d1320fc _UIFocusItemContainerAddChildItemsInContextWithOptions + 596 (UIFocusItemContainer.m:183) 11 UIKitCore 0x19d131b98 _UIFocusRegionSearchContextAddChildItemsInEnvironmentContainer + 648 (_UIFocusRegion.m:108) 12 UIKitCore 0x19d131398 _UIFocusRegionSearchContextSearchForFocusRegionsInEnvironment + 564 (_UIFocusRegion.m:140) 13 UIKitCore 0x19db1d244 -[_UIFocusRegionContainerProxy _searchForFocusRegionsInContext:] + 140 (_UIFocusRegionContainerProxy.m:184) 14 UIKitCore 0x19db28498 -[_UIFocusMapSnapshot addRegionsInContainer:] + 2720 (_UIFocusMapSnapshot.m:531) 15 UIKitCore 0x19d1320fc _UIFocusItemContainerAddChildItemsInContextWithOptions + 596 (UIFocusItemContainer.m:183) 16 UIKitCore 0x19d131b98 _UIFocusRegionSearchContextAddChildItemsInEnvironmentContainer + 648 (_UIFocusRegion.m:108) 17 UIKitCore 0x19d131398 _UIFocusRegionSearchContextSearchForFocusRegionsInEnvironment + 564 (_UIFocusRegion.m:140) 18 UIKitCore 0x19db1d244 -[_UIFocusRegionContainerProxy _searchForFocusRegionsInContext:] + 140 (_UIFocusRegionContainerProxy.m:184) 19 UIKitCore 0x19db28498 -[_UIFocusMapSnapshot addRegionsInContainer:] + 2720 (_UIFocusMapSnapshot.m:531) 20 UIKitCore 0x19d1320fc _UIFocusItemContainerAddChildItemsInContextWithOptions + 596 (UIFocusItemContainer.m:183) 21 UIKitCore 0x19d131b98 _UIFocusRegionSearchContextAddChildItemsInEnvironmentContainer + 648 (_UIFocusRegion.m:108) 22 UIKitCore 0x19d131398 _UIFocusRegionSearchContextSearchForFocusRegionsInEnvironment + 564 (_UIFocusRegion.m:140) 23 UIKitCore 0x19db1d244 -[_UIFocusRegionContainerProxy _searchForFocusRegionsInContext:] + 140 (_UIFocusRegionContainerProxy.m:184) 24 UIKitCore 0x19db28498 -[_UIFocusMapSnapshot addRegionsInContainer:] + 2720 (_UIFocusMapSnapshot.m:531) 25 UIKitCore 0x19d1320fc _UIFocusItemContainerAddChildItemsInContextWithOptions + 596 (UIFocusItemContainer.m:183) 26 UIKitCore 0x19d131b98 _UIFocusRegionSearchContextAddChildItemsInEnvironmentContainer + 648 (_UIFocusRegion.m:108) 27 UIKitCore 0x19d131398 _UIFocusRegionSearchContextSearchForFocusRegionsInEnvironment + 564 (_UIFocusRegion.m:140) 28 UIKitCore 0x19db1d244 -[_UIFocusRegionContainerProxy _searchForFocusRegionsInContext:] + 140 (_UIFocusRegionContainerProxy.m:184) 29 UIKitCore 0x19db28498 -[_UIFocusMapSnapshot addRegionsInContainer:] + 2720 (_UIFocusMapSnapshot.m:531) 30 UIKitCore 0x19d1320fc _UIFocusItemContainerAddChildItemsInContextWithOptions + 596 (UIFocusItemContainer.m:183) 31 UIKitCore 0x19d131b98 _UIFocusRegionSearchContextAddChildItemsInEnvironmentContainer + 648 (_UIFocusRegion.m:108) 32 UIKitCore 0x19d131398 _UIFocusRegionSearchContextSearchForFocusRegionsInEnvironment + 564 (_UIFocusRegion.m:140) 33 UIKitCore 0x19db1d244 -[_UIFocusRegionContainerProxy _searchForFocusRegionsInContext:] + 140 (_UIFocusRegionContainerProxy.m:184) 34 UIKitCore 0x19db28498 -[_UIFocusMapSnapshot addRegionsInContainer:] + 2720 (_UIFocusMapSnapshot.m:531) 35 UIKitCore 0x19d1320fc _UIFocusItemContainerAddChildItemsInContextWithOptions + 596 (UIFocusItemContainer.m:183) 36 UIKitCore 0x19d131b98 _UIFocusRegionSearchContextAddChildItemsInEnvironmentContainer + 648 (_UIFocusRegion.m:108) 37 UIKitCore 0x19d131398 _UIFocusRegionSearchContextSearchForFocusRegionsInEnvironment + 564 (_UIFocusRegion.m:140) 38 UIKitCore 0x19db1d244 -[_UIFocusRegionContainerProxy _searchForFocusRegionsInContext:] + 140 (_UIFocusRegionContainerProxy.m:184) 39 UIKitCore 0x19db28498 -[_UIFocusMapSnapshot addRegionsInContainer:] + 2720 (_UIFocusMapSnapshot.m:531) 40 UIKitCore 0x19d132e08 -[_UIFocusMapSnapshot _capture] + 424 (_UIFocusMapSnapshot.m:403) 41 UIKitCore 0x19db2675c -[_UIFocusMapSnapshot _initWithSnapshotter:mapArea:searchArea:] + 476 (_UIFocusMapSnapshot.m:171) 42 UIKitCore 0x19d130dcc -[_UIFocusMapSnapshotter captureSnapshot] + 192 (_UIFocusMapSnapshotter.m:137) 43 UIKitCore 0x19db2045c -[_UIFocusMap _inferredDefaultFocusItemInEnvironment:] + 136 (_UIFocusMap.m:168) 44 UIKitCore 0x19daffd2c -[_UIFocusEnvironmentPreferenceEnumerationContext _inferPreferencesForEnvironment:] + 140 (_UIFocusEnvironmentPreferenceEnumerator.m:313) 45 UIKitCore 0x19d127ab4 -[_UIFocusEnvironmentPreferenceEnumerationContext _resolvePreferredFocusEnvironments] + 104 (_UIFocusEnvironmentPreferenceEnumerator.m:250) 46 UIKitCore 0x19d127394 -[_UIFocusEnvironmentPreferenceEnumerationContext preferredEnvironments] + 36 (_UIFocusEnvironmentPreferenceEnumerator.m:184) 47 UIKitCore 0x19d126e94 _enumeratePreferredFocusEnvironments + 400 (_UIFocusEnvironmentPreferenceEnumerator.m:503)

Hi! I've encountered strange bug in iOS 26. The MultiDatePicker component exhibits unreliable behavior when attempting to deselect previously chosen dates. Users often need to tap a selected date multiple times (e.g., tap to deselect, tap to re-select, then tap again to deselect) for the UI to correctly register the deselection and update the displayed state. This issue does not occur on iOS 18 or Xcode 26 previews, where MultiDatePicker functions as expected, allowing single-tap deselection. The bug only occurs on physical device or simulator. I can't lie, I have multidatepicker as crucial component in my larger app and can't really find a solution to this. Has anyone encountered this problem before? Here is the code to replicate the issue: import SwiftUI struct ContentView: View {     @ State private var selectedDates: Set = []     var body: some View {         NavigationStack {             Form {                 Section {                     MultiDatePicker("Select Dates", selection: $selectedDates)                 } header: {                     Text("MultiDatePicker Bug Test")                 }                 Section {                     Text("Selected Dates Count: (selectedDates.count)")                     ForEach(Array(selectedDates).sorted(by: {                         Calendar.current.date(from: $0)! < Calendar.current.date(from: $1)!                     }), id: .self) { dateComponent in                         if let date = Calendar.current.date(from: dateComponent) {                             Text(date.formatted(date: .long, time: .omitted))                         }                     }                 } header: {                     Text("Current State of Selected Dates")                 }             }             .navigationTitle("Date Picker Bug")         }     } } #Preview {     ContentView() }

Bug: Software Update UI state desync on iPadOS 27.0 RC (build 24A435) Reproduction Steps Complete downloading OTA system update, Software Update page shows Chinese localized button "现在更新" (Update Now). Go to iPad Storage and delete the downloaded OTA package. Navigate back to Software Update page immediately, NO reboot and NO manual page refresh. Expected Behavior The UI should detect that the local update file was removed, and switch the button to "下载" (Download). Actual Behavior The interface keeps displaying the "现在更新" button. The UI state is out of sync with the real existence of the downloaded OTA file. I did NOT tap the update button to prevent potential system risk; the state inconsistency itself is the bug. Full screen recording and sysdiagnose logs were submitted in Feedback Assistant report: FB24741350 I want to check whether other developers have encountered the same bug on iPadOS 27.0 RC. This UI inconsistency may confuse end users and bring potential safety misunderstanding, so I hope this issue can be prioritized and fixed before the official 27.0 release.

Hello, I’m using the latest version of Xcode, 26.6. I’m unable to permanently delete old installed iOS platform versions. I remove them from Xcode settings, and the deletion appears to complete successfully, but after rebooting my Mac they appear again, as if nothing had changed. Do you have any suggestions for how to remove them correctly and permanently?

Hi, I'm posting a boot crash here. Environment Hardware: Macbook M5 Pro OS Version: macOS 26.3.1 (25D2128) and matching version of KDK from official apple download page Kernel Version: Darwin Kernel Version 25.3.0 Reproducibility: Consistent Here is my panic log --- I truncated one field "SOCDNandContainer" as the original log is too long to post, hitting the size limit. I followed a blog post to boot the development kernel as the ReadMe file from KDK only contains instructions for Intel Macs. https://jaitechwriteups.blogspot.com/2025/10/boot-custom-macos-kernel-on-macos-apple.html I've tried a few 26.2 KDKs before 26.3.1 public launch, and they all showed same errors (26.1 and 26.0 KDKs don't have any development kernel for T8142 chip). Also, I own two fresh M5 Pro, and it is consistent across the machines. The highlight is panic(cpu 8 caller 0xfffffe0050e18010): [Exclaves] $JgOSLogServerComponent.RedactedLogServer.init(logServerNotific:OSLogServerComponent\/OSLogServerComponent_Swift.swift:815: Fatal error: invalid rawValue for TightbeamComponents.RedactedLogSer at PC ... Is this a genuine bug or am I following a wrong guide to boot the development kernel? I don't think the blog is wrong because I'm able to boot the "release" kernel included in the KDK on the same M5 Pro, and the "development" kernel on M4 Mac Mini, using the same routine. Just to be clear, I'm not compiling XNU myself, but am using the ones included in the kit.

Hello Apple engineers and developers, I’m the owner/developer of https://mated.uz/, a legitimate SaaS platform for businesses in Uzbekistan. We have been experiencing a serious issue with Safari for approximately one month: Safari incorrectly displays a red “Fraudulent Website Warning” for our website. The important part is that the problem appears to be Safari-specific. The website works normally in: Chrome Microsoft Edge Firefox other browsers The website is a legitimate business platform and does not contain phishing pages, malware, deceptive content, or attempts to impersonate Apple or another service. What we have already done We have repeatedly submitted the domain for review through Apple’s website review process, including several requests over the past month. However, the warning is still present and we have not received a clear explanation of what is triggering the classification. We have also checked the website and its infrastructure for common causes: HTTPS / TLS certificate is valid No intentional redirects to suspicious domains No phishing or credential-harvesting pages No malware No deceptive content The website works correctly in other browsers The domain is actively used by a real operating business The problem This is becoming a real business issue because users who open our website from an iPhone or Mac using Safari may see a warning that effectively tells them our business is fraudulent. For a SaaS company, this significantly damages user trust and can prevent potential customers from accessing the platform. We would really appreciate guidance from Apple engineers on the following: How can we determine why Safari has classified our domain as fraudulent? Does Safari use an independent reputation database for this warning, separate from Google Safe Browsing? Is there any technical information or diagnostic data that website owners can use to identify the reason for the classification? Is there another escalation/review channel when the standard Website Review requests do not resolve a false positive? Are there specific DNS, hosting, redirect, TLS, domain-reputation, or third-party-script signals that we should investigate? We are happy to provide screenshots, domain information, security scan results, or any other technical information required. This appears to be a false positive affecting Safari only, and we would really appreciate any guidance on how to get the domain reviewed and the warning removed. Thank you.