I have nvALT 2.2 (122) set to launch at startup on macOS 10.12 with the window hidden. Whenever I log in, the following error message is shown.

Here are further details:
Exception Name: NSInternalInconsistencyException
Description: Invalid parameter not satisfying: [self canBecomeMainWindow]
User Info: (null)
0 CoreFoundation 0x00007fff8740c7bb __exceptionPreprocess + 171
1 libobjc.A.dylib 0x00007fff9bb79a2a objc_exception_throw + 48
2 CoreFoundation 0x00007fff87411312 +[NSException raise:format:arguments:] + 98
3 Foundation 0x00007fff88e64390 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 195
4 AppKit 0x00007fff852d5044 -[NSWindow _changeJustMain] + 309
5 nvALT 0x00000001038553f7 nvALT + 66551
6 Foundation 0x00007fff88e0ac88 __NSFireDelayedPerform + 417
7 CoreFoundation 0x00007fff8738cf44 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
8 CoreFoundation 0x00007fff8738cbd3 __CFRunLoopDoTimer + 1075
9 CoreFoundation 0x00007fff8738c72a __CFRunLoopDoTimers + 298
10 CoreFoundation 0x00007fff873842f1 __CFRunLoopRun + 2081
11 CoreFoundation 0x00007fff87383874 CFRunLoopRunSpecific + 420
12 HIToolbox 0x00007fff86923f6c RunCurrentEventLoopInMode + 240
13 HIToolbox 0x00007fff86923da1 ReceiveNextEventCommon + 432
14 HIToolbox 0x00007fff86923bd6 _BlockUntilNextEventMatchingListInModeWithFilter + 71
15 AppKit 0x00007fff8501a5f5 _DPSNextEvent + 1093
16 AppKit 0x00007fff8572a8eb -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1637
17 AppKit 0x00007fff8500efbd -[NSApplication run] + 926
18 AppKit 0x00007fff84fd9a8a NSApplicationMain + 1237
19 libdyld.dylib 0x00007fff9c455255 start + 1
20 ??? 0x0000000000000001 0x0 + 1
@mongobuggy Thanks for the report.
Having trouble reproducing your crash though, so I need you to answer a few questions:
Thanks for helping.
seems fixed on 2.2 (122)
Thanks for the response @elasticthreads But, as I said, I am running 2.2 (122) and experiencing the problem with this version.
In answer to your questions:
I’ve now assigned a system-wide keyboard shortcut as a permanent workaround, but others may have this problem.
what does the system wide shortcut do?
It launches the app. It’s the same as the one assigned as the nvALT bring-to-front hotkey, so I can use it without the app set to launch at startup. @elasticthreads
I'm having the exact same errors, in the exact same conditions — I have the app set to launch on startup, and that's the only time I see the crash.
Exception Name: NSInternalInconsistencyException
Description: Invalid parameter not satisfying: [self canBecomeMainWindow]
User Info: (null)
0 CoreFoundation 0x00007fff804c052b exceptionPreprocess + 171
1 libobjc.A.dylib 0x00007fff94b98cad objc_exception_throw + 48
2 CoreFoundation 0x00007fff804c5232 +[NSException raise:format:arguments:] + 98
3 Foundation 0x00007fff81ef8390 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 195
4 AppKit 0x00007fff7e389044 -[NSWindow _changeJustMain] + 309
5 nvALT 0x0000000105d9d3f7 nvALT + 66551
6 Foundation 0x00007fff81e9ec88 __NSFireDelayedPerform + 417
7 CoreFoundation 0x00007fff8043fe14 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION + 20
8 CoreFoundation 0x00007fff8043fa9f __CFRunLoopDoTimer + 1071
9 CoreFoundation 0x00007fff8043f5fa __CFRunLoopDoTimers + 298
10 CoreFoundation 0x00007fff80437021 __CFRunLoopRun + 2065
11 CoreFoundation 0x00007fff804365b4 CFRunLoopRunSpecific + 420
12 HIToolbox 0x00007fff7f9d7f6c RunCurrentEventLoopInMode + 240
13 HIToolbox 0x00007fff7f9d7da1 ReceiveNextEventCommon + 432
14 HIToolbox 0x00007fff7f9d7bd6 _BlockUntilNextEventMatchingListInModeWithFilter + 71
15 AppKit 0x00007fff7e0ce5f5 _DPSNextEvent + 1093
16 AppKit 0x00007fff7e7de8eb -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1637
17 AppKit 0x00007fff7e0c2fbd -[NSApplication run] + 926
18 AppKit 0x00007fff7e08da8a NSApplicationMain + 1237
19 libdyld.dylib 0x00007fff95476255 start + 1
I ran into the same error (OP) while using it regularly (not on startup -- just typing in a note I had been working on). It caught me off guard, as the app hasn't had any problems for me in this build.
This should be fixed in the updates we released this week. Please report back if its not.
Thanks, @elasticthreads; seems fixed to me.