Posts

Post marked as solved
7 Replies
The problem turned out to be an older copy of the app on my disk and macOS getting confused and looking in the wrong place. I'm adding a Widget to an existing app that doesn't currently have one. I have the current, App Store version in /Applications. I've been running the updated version from Xcode or exporting it to my desktop and running it from there. The Widget itself -- as noted in the question -- runs just fine. But it seems that when looking for the Intent used for the configuration, it prefers to look in /Application rather than the Xcode version. As soon as I deleted the original app, the widget and its settings immediately started working.
Post not yet marked as solved
1 Replies
I asked the same question about Intel Macs: https://developer.apple.com/forums/thread/659420?answerId=637749022#637749022 Currently one person saying that it works, but I still have not had any luck.
Post marked as solved
7 Replies
This is still not working for me. Clearly I'm doing something different to Hiren, so to be clear, here are the steps: Create a new Mac project Add a new Widget target Change the generated Intent, adding a parameter. You also need to add a "Siri Dialog Prompt" Click "Run" Click "Info" in the Widget Simulator Click "Configure Intent" I don't see my optional parameter. When I click "Done" it says "Unable to Load." Back in my main project, the exact same Intent and Widget works just fine on iOS and iPadOS. Is there an extra step for the Mac? Is there a bug? I'm running Big Sur b9 and Xcode 12.2b2 now.
Post marked as solved
20 Replies
To answer my own question... I installed beta 3, then uncompressed beta 4 and copied it on top of b3. I can now run Xcode. It's possible that there's a mising file in the download, but I’ve not been able to reproduce the problem again now that I have it working.
Post marked as solved
20 Replies
Do you get a stack trace/crash report? When I try to start on a MacBook (clean install of Mojave) I get this;Application Specific Information: ProductBuildVersion: 11M374r ASSERTION FAILURE in /Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-14897.4/IDEFoundation/Initialization/IDEInitialization.m:790 Details: dlhandle is NULL. dylibPath: /Applications/Xcode-beta.app/Contents/Developer/usr/lib/libMainThreadChecker.dylib Function: void _IDEInitializeMainThreadChecker() Thread: {number = 1, name = main} Hints: Backtrace: 0 -[IDEAssertionHandler handleFailureInFunction:fileName:lineNumber:assertionSignature:messageFormat:arguments:] (in IDEKit) 1 _DVTAssertionHandler (in DVTFoundation) 2 _DVTAssertionFailureHandler (in DVTFoundation) 3 _IDEInitializeMainThreadChecker (in IDEFoundation) 4 IDEInitialize (in IDEFoundation) 5 -[IDEApplicationController applicationWillFinishLaunching:] (in IDEKit) 6 __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ (in CoreFoundation) 7 ___CFXRegistrationPost_block_invoke (in CoreFoundation) 8 _CFXRegistrationPost (in CoreFoundation) 9 ___CFXNotificationPost_block_invoke (in CoreFoundation) 10 -[_CFXNotificationRegistrar find:object:observer:enumerator:] (in CoreFoundation) 11 _CFXNotificationPost (in CoreFoundation) 12 -[NSNotificationCenter postNotificationName:object:userInfo:] (in Foundation) 13 -[NSNotificationCenter(DVTNSNotificationCenterAdditions_MRR) _dvt_postNotificationName:object:userInfo:] (in DVTFoundation) 14 -[NSApplication finishLaunching] (in AppKit) 15 -[DVTApplication finishLaunching] (in DVTKit) 16 -[NSApplication run] (in AppKit) 17 NSApplicationMain (in AppKit) 18 main (in Xcode) 19 start (in libdyld.dylib) abort() called\ Application Specific Signatures: dlhandle != ((void*)0)To be clear, this is on start. There is no project; there's no history. It runs just fine on another machine, a MacBook Pro.