Will shares transfer ever work again?

Richard Anderson

Process: Quicken [570]
Path: /Applications/Quicken.app/Contents/MacOS/Quicken
Identifier: com.quicken.Quicken
Version: 5.11.1 (511.25673.100)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Quicken [570]
User ID: 501

Date/Time: 2019-07-13 11:50:11.128 -0500
OS Version: Mac OS X 10.14.5 (18F132)
Report Version: 12
Anonymous UUID: 880A8CE5-CB95-B132-4592-4D767AE5F701


Time Awake Since Boot: 220 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Application Specific Information:
[Begin CrashInfo Version:2]
Timestamp: 2019-07-13 11:50:10 -0500
OS X Version: 10.14.5
App Version: 5.11.1
Aborted: Unhandled Exception
Is Main Thread?: Yes
Thread Name:
Exception Name: NSInvalidArgumentException
Reason: -[__NSCFNumber compare:]: nil argument
[End CrashInfo Version:2]

Alternate Stack Trace:
0 CoreFoundation 0x00007fff4230ccfd __exceptionPreprocess + 256
1 libobjc.A.dylib 0x00007fff6c9b2a17 objc_exception_thro

jacobs

Will it ever work again? It's a new feature just added in the most recent update, so it's not as if a long-standing feature has been removed. It sounds like it could be encountering something in your data that it's not expecting, resulting in a crash.

A crash report in this forum isn't likely to be useful, since it's mostly fellow users here. There are two ways you can pursue this. First, use the Report a Problem page on the Quicken Help menu to report this. The good thing is hard crashes typically are most likely to get attention; the bad thing is you won't get any feedback, as this is a one-way channel of communication. The other thing you can do is contact by phone during the week when they're open. A Quicken representative can screen share your Mac to see what you're doing and seeing, and they can capture log files to escalate an issue.

jacobs

Will it ever work again? It's a new feature just added in the most recent update, so it's not as if a long-standing feature has been removed. It sounds like it could be encountering something in your data that it's not expecting, resulting in a crash.

A crash report in this forum isn't likely to be useful, since it's mostly fellow users here. There are two ways you can pursue this. First, use the Report a Problem page on the Quicken Help menu to report this. The good thing is hard crashes typically are most likely to get attention; the bad thing is you won't get any feedback, as this is a one-way channel of communication. The other thing you can do is contact by phone during the week when they're open. A Quicken representative can screen share your Mac to see what you're doing and seeing, and they can capture log files to escalate an issue.

Richard Anderson

I did send several crash reports (single share transfer, all shares in account transfer, a different stock share transfer).

I didn't realize share transfer was new in QM. I've used it in QM for a long time including today when I transferred those same 25 stock holdings in my Q Windows. I've been trying to finish converting everything from QW to QM, but so far the QM falls short so I'm still stuck with using both.