It happened that I removed a profile with rules depending on it, and ControlPlane crashed.
Afterwhile, it crashed on every subsequent attempt to start it.
I removed all ControlPlane saved state and preferences, but still crashes on startup.
$ find $HOME -iname *controlplane*
(no files found)
2014-06-17 11:06:31.994 ControlPlane[92330:507] 1090
2014-06-17 11:06:34.481 ControlPlane[92330:12a0b] An uncaught exception was raised
2014-06-17 11:06:34.482 ControlPlane[92330:12a0b] *** -[__NSSetM addObject:]: object cannot be nil
2014-06-17 11:06:34.482 ControlPlane92330:12a0b
2014-06-17 11:06:34.483 ControlPlane[92330:12a0b] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[__NSSetM addObject:]: object cannot be nil'
*** First throw call stack:
0 CoreFoundation 0x00007fff8a9ed25c __exceptionPreprocess + 172
1 libobjc.A.dylib 0x00007fff956eae75 objc_exception_throw + 43
2 CoreFoundation 0x00007fff8a90ca16 -[__NSSetM addObject:] + 790
3 ControlPlane 0x00000001050a0688 -[CPController changeActiveContextsBasedOnGuesses:] + 349
4 ControlPlane 0x00000001050a03d9 -[CPController doUpdateForReal] + 327
5 ControlPlane 0x00000001050a282e -[CPController doUpdate] + 80
6 libdispatch.dylib 0x00007fff94f8c28d _dispatch_client_callout + 8
7 libdispatch.dylib 0x00007fff94f8e885 _dispatch_source_invoke + 413
8 libdispatch.dylib 0x00007fff94f8e617 _dispatch_queue_drain + 359
9 libdispatch.dylib 0x00007fff94f8f9c1 _dispatch_queue_invoke + 110
10 libdispatch.dylib 0x00007fff94f8df87 _dispatch_root_queue_drain + 75
11 libdispatch.dylib 0x00007fff94f8f177 _dispatch_worker_thread2 + 40
12 libsystem_pthread.dylib 0x00007fff93486ef8 _pthread_wqthread + 314
13 libsystem_pthread.dylib 0x00007fff93489fb9 start_wqthread + 13
libc++abi.dylib: terminating with uncaught exception of type NSException
Abort trap: 6
When you say profile, are you talking about a network location?
Or are you referring to a context?
I mean a ControlPlane context
Thanks for reporting, Federico (@fferri). That problem has already been reported to us and I pushed a fix for it to the main branch. When @dustinrue releases the next official (or developer's) version of CP to the public, the fix will be a part of it. If you want us to give you a developer's build ahead of that, please, let us know.