Crash Error on Launch Every Time
M
Mike Halliburton
Getting this error every time since I installed the beta app (did not have this issue with the previous Apple Store version). I can just hit the "Continue" button and the app otherwise seems to function as expected. Have attached a screenshot and text file with the error details, which I'll also copy and paste here. Let me know if I can provide additional details to troubleshoot...
SYSTEM:
M1 Max, 32GB, Sequoia 15.3.2
ERROR DETAILS:
Exception Name: NSInvalidArgumentException
Description: -[HedyAI.AppDelegate applicationDidFinishLaunching:]: unrecognized selector sent to instance 0x600001e697d0
User Info: (null)
0 CoreFoundation 0x000000018850ee80 __exceptionPreprocess + 176
1 libobjc.A.dylib 0x0000000187ff6cd8 objc_exception_throw + 88
2 CoreFoundation 0x00000001885c41d8 -[NSObject(NSObject) __retain_OA] + 0
3 CoreFoundation 0x000000018847b5d4 ___forwarding___ + 964
4 CoreFoundation 0x000000018847b150 _CF_forwarding_prep_0 + 96
5 HedyAI 0x0000000102254670 $s6HedyAI11AppDelegateC29applicationDidFinishLaunchingyy10Foundation12NotificationVF + 384
6 HedyAI 0x0000000102254bd4 $s6HedyAI11AppDelegateC29applicationDidFinishLaunchingyy10Foundation12NotificationVFToTm + 120
7 CoreFoundation 0x0000000188491370 __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 148
8 CoreFoundation 0x000000018852220c ___CFXRegistrationPost_block_invoke + 88
9 CoreFoundation 0x0000000188522154 _CFXRegistrationPost + 436
10 CoreFoundation 0x000000018845ffac _CFXNotificationPost + 732
11 Foundation 0x000000018961a6b8 -[NSNotificationCenter postNotificationName:object:userInfo:] + 88
12 AppKit 0x000000018c01b48c -[NSApplication _postDidFinishNotification] + 284
13 AppKit 0x000000018c01b23c -[NSApplication _sendFinishLaunchingNotification] + 172
14 AppKit 0x000000018c01969c -[NSApplication(NSAppleEventHandling) _handleAEOpenEvent:] + 500
15 AppKit 0x000000018c0192a4 -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 488
16 Foundation 0x00000001896434ac -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 316
17 Foundation 0x00000001896432a4 _NSAppleEventManagerGenericHandler + 80
18 AE 0x000000018fa3b134 _AppleEventsCheckInAppWithBlock + 13904
19 AE 0x000000018fa3aa58 _AppleEventsCheckInAppWithBlock + 12148
20 AE 0x000000018fa33fa4 aeProcessAppleEvent + 488
21 HIToolbox 0x0000000193927210 AEProcessAppleEvent + 68
22 AppKit 0x000000018c012b40 _DPSNextEvent + 1420
23 AppKit 0x000000018c978c24 -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 688
24 AppKit 0x000000018c005874 -[NSApplication run] + 480
25 AppKit 0x000000018bfdc068 NSApplicationMain + 888
26 HedyAI 0x0000000102255070 main + 36
27 dyld 0x0000000188034274 start + 2840
Julian
Bodo Folger: Please do let us know if the crash is still happening in version 2.0.4 or later. You can download the latest version here: https://macos.hedy.bot/
Canny AI
Merged in a post:
Crashes constantly.
Bodo Folger
Julian
Thank you Mike Halliburton! The next build (2.0.3) will contain a potential fix for this.
M
Mike Halliburton
Julian Awesome!
M
Mike Halliburton
Hey Julian, I just tried using Hedy for a Zoom meeting and found that it simply never initiated despite my having pressed the button and received confirmation moments before the meeting started. This had happened once before, but I thought perhaps it was user error. However, it's been twice in a row now, and I realized I haven't successfully initiated a session since replacing the stable app (from Apple's App Store) with the beta version. The stable app had been working fine previously. Thinking I may go back to that version for now...
M
Mike Halliburton
If I want to try out the next beta version, should I install it alongside the stable app (if that's possible) or replace the stable app? Would you recommend uninstalling the former before installing the beta app or merely writing over the existing one? Thanks
Julian
Mike Halliburton: You can definitely run the old app from the Mac App Store side-by-side with the new, native app for now. I'm sorry to hear that you're having issues with the new app. I'd be curious if those issues still persist in the latest version 2.0.4.
(Also my apologies for missing your response last week)