Hello, The following simple code leads to memory leak IOHIDManagerRef hidManager = IOHIDManagerCreate(kCFAllocatorDefault, kIOHIDManagerOptionNone); ... IOHIDManagerSetDeviceMatching(hidManager, matchingCriteria); CFRelease(matchingCriteria); if (IOHIDManagerOpen(hidManager, kIOHIDOptionsTypeNone) != kIOReturnSuccess) { return 1; } ... if (IOHIDManagerClose(hidManager, kIOHIDOptionsTypeNone) != kIOReturnSuccess) { return 1; } CFRelease(hidManager); The following leaks report: STACK OF 2 INSTANCES OF ROOT LEAK: : 17 dyld 0x19b3aeb98 start + 6076 16 a.out 0x1027147e4 main + 200 15 com.apple.framework.IOKit 0x19f6781b8 __ApplyToDevices + 100 14 com.apple.CoreFoundation 0x19b801cfc CFSetApplyFunction + 224 13 com.apple.CoreFoundation 0x19b801dc0 CFBasicHashApply + 148 12 com.apple.CoreFoundation 0x19b801f94 __CFSetApplyFunction_block_invoke + 28 11 com.apple.framework.IOKit 0x19f6784c8 __IOHIDManagerDeviceApplier + 76 10 com.apple.framework.IOKit 0x19f5e18ec IOHIDDeviceOpen + 56 9 com.apple.iokit.IOHIDLib 0x10299
Search results for
Swift 6
49,212 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Still present in iOS 26 beta 6. I suspect the reporting feature will be removed from iOS in the near future.
Topic:
App & System Services
SubTopic:
General
Tags:
We have exact same issue in our 6 frameworks since recently. All Xcode Cloud workflows are not visible in Xcode and web. At the same time we can see that workflows still exist via App Store Connect API - and they actually trigger and are able to post GitHub checks. Unfortunately the URLs in GitHub checks are broken and lead to nowhere. We are also blocked by authorizing new dependencies, which always redirects to website, and website always shows a setup screen as if Xcode Cloud is not configured.
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
I am building an electron app bundled with python. My code signing was fast, but when it came to notarization, it has already taken over 6+ hours. How can I speed things up?
I'd also recommend contacting QT suggesting they file their own bug(s) and/or contact DTS to talk about options.> Yes, it is done. In the meantime, I have installed macOS 26 beta 6 and the icon is back!
Topic:
App & System Services
SubTopic:
Core OS
Environment • Device: iOS 26 Developer Beta 5 (23A5308g) • Xcode: 16.3 Short description The app crashes the moment the user tries to long-press to select text inside a WKWebView, double-tap an image with Text (magnifier appears) The exception is CALayer position contains NaN. frame = (nan,0;0,48) chorPoint=(inf, 0) and it is thrown in the UI process. Build & run any project that hosts a WKWebView. Inject the following CSS via script (this is what we do to suppress the native callout menu): WKWebView *webView = [[WKWebView alloc] initWithFrame:self.view.bounds configuration:[WKWebViewConfiguration new]]; NSString *js = @document.documentElement.style.webkitUserSelect='none'; document.documentElement.style.webkitTouchCallout='none';; [webView evaluateJavaScript:js completionHandler:nil]; [self.view addSubview:webView]; Incident Identifier: EE6FB046-5087-4F15-A72D-A74965347A30 CrashReporter Key: 29e8e58e02a07557adb4ce3f463d764f3ce8bbd5 Hardware Model: iPhone16,1 Process: wallet [642] Path: /private/var/cont
I sincerely apologize for misstating the version number. This issue first appeared after beta 5 and persists even in beta 6 (25A5338b).
Topic:
Community
SubTopic:
Apple Developers
Tags:
Same in beta 6
Topic:
Community
SubTopic:
Apple Developers
Tags:
OS version:15.6 (24G84). mac mini m 4 Xcode:16.4 stack: Translated Report (Full Report Below) Process: Xcode [5261] Path: /Applications/Xcode.app/Contents/MacOS/Xcode Identifier: com.apple.dt.Xcode Version: 16.4 (23792) Build Info: IDEApplication-23792000000000000~2 (16F6) App Item ID: 497799835 App External ID: 874973124 Code Type: ARM-64 (Native) Parent Process: launchd [1] User ID: 501 Date/Time: 2025-08-11 19:57:18.7642 +0800 OS Version: macOS 15.6 (24G84) Report Version: 12 Anonymous UUID: 314F3813-7BB3-0263-1826-79D64A62D963 Time Awake Since Boot: 700 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BREAKPOINT (SIGTRAP) Exception Codes: 0x0000000000000001, 0x00000001ab5dc1f8 Termination Reason: Namespace SIGNAL, Code 5 Trace/BPT trap: 5 Terminating Process: exc handler [5261] Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libswiftCore.dylib 0x1ab5dc1f8 assertionFailure(:_:file:line:flags:) + 176 1 libswiftCore.dylib 0x1a
The code is called on the main thread. According to the crash report, thread 0 makes that assignment, Looking at the crash log, the abort originates here: 4 libobjc.A.dylib 0x00000001818d7fc0 _objc_fatal(char const*, ...) + 44 (objc-errors.mm:232) 5 libobjc.A.dylib 0x00000001818a6d78 weak_register_no_lock + 396 (objc-weak.mm:423) 6 libobjc.A.dylib 0x00000001818a6b40 objc_storeWeak + 472 (NSObject.mm:408) As it happen, you don't have to guess at why weak_register_no_lock failed, as the project is opensource. Here is the line that's crashing: _objc_fatal(Cannot form weak reference to instance (%p) of class %s. It is possible that this object was over-released, or is in the process of deallocation., (void*)referent, object_getClassName((id)referent)); That leads to here: and at the same time thread 16 is calling [NSImageView asynchronousPreparation:prepareResultUsingParameters:]. Unfortunately, I wouldn't necessarily assume this call is directly involved. From the large context in the logs you sent to
Topic:
UI Frameworks
SubTopic:
AppKit
Tags:
I want to fully control the BLE send timing myself, instead of relying on the iOS system. When I try to send a large data block using BLE (i.e., splitting it and sending multiple times), I follow Apple’s official guide. However, after the first successful updateValue() call in my loop, the second call always fails unless I wait for the peripheralManagerIsReady(toUpdateSubscribers:) callback. This callback timing is managed by the system, so I can’t control exactly when I can send the next packet. If I send data manually by clicking a button, updateValue() always returns true—even if I add a long delay (like sleep(10)) between calls. But in a loop, after the first send, updateValue() returns false until the thread leaves or the callback occurs. I suspect this is a thread or queue issue blocking subsequent sends. I also tried using DispatchQueue.global().async {} in the loop, but the result is the same. Is there any way to fully control when I call updateValue(), without waiting for peripheralManagerIsReady()?
Hi, I was wondering if it's possible (and advisable) to use the new glass effects available in iOS 26 in Swift Charts? For example, in a chart like the one in the image I've attached to this post, I was looking to try adding a .glassEffect modifier to the BarMarks to see how that would look and feel. However, it seems it's not available directly on the BarMark (ChartContent) type, and I'm having trouble adding it in other ways too, such as using in on the types I supply to modifiers like foregroundStyle or clipShape. Am I missing anything? Maybe it's just not advisable or necessary to use glass effects within Charts?
The core development is in Swift.
Topic:
Graphics & Games
SubTopic:
Metal
Tags:
@DTS Engineer, I'm still getting the issue even with the Foundation module qualifier in the front of NSXPCInterface. The strangest thing is that I have others on my team that can build successfully with the same commit on the same version of XCode. I suspect something more environmental to my machine. I noticed that when I Jump to Definition on NSXPCInterface, XCode sometimes points me to the Swift definition of the interface, like below: @available(macOS 10.8, *) open class NSXPCInterface : NSObject { public /*not inherited*/ init(with protocol: Protocol) unowned(unsafe) open var `protocol`: Protocol //... } and other times it will point me to NSXPCConnection.h, like below: API_AVAILABLE(macos(10.8), ios(6.0), watchos(2.0), tvos(9.0)) @interface NSXPCInterface : NSObject // Factory method to get an NSXPCInterface instance for a given protocol. Most interfaces do not need any further configuration. Interfaces with collection classes or additional proxy objects should be configured using the methods b
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Any updates for dev beta 6?
Topic:
Community
SubTopic:
Apple Developers
Tags: