You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Console output shows an uncaught exception: 2015/13/04 14:11:33.126 ControlPlane[29302]: *** -[__NSCFCalendar components:fromDate:]: date cannot be nil
I'm not sure what format if any is expected for the date, but my region settings are for Japan so I wonder if there is a format conversion with a nil return value. Let me know if more detail is required and I'll see what debug info I can dig up. Thanks for any help!
The text was updated successfully, but these errors were encountered:
Can you download http://www.controlplaneapp.com/download/ci and see if it works around the issue for you? It'll prevent a crash but the evidence won't work. You might need to remove and re-add the rule.
I merged some extra code changes today, to prevent CP from crashing and to provide better reporting in CP log (the one at the "Advanced" tab in "Preferences") on errors when parsing parameters of "Time of day" rules.
Dustin may create another custom build with those changes and give it to you sometime around these days. When you have that one, try it and let us know if (1) it crashes or not on your system and (2) the rule works or not [and if the rule does not work, check the log at the "Advanced" tab in "Parameters" and let us know if you see messages on errors with parsing the rule parameters and what explicitly those messages say].
ControlPlane has been crashing on launch for me, crash dump as follows:
Console output shows an uncaught exception:
2015/13/04 14:11:33.126 ControlPlane[29302]: *** -[__NSCFCalendar components:fromDate:]: date cannot be nil
I'm not sure what format if any is expected for the date, but my region settings are for Japan so I wonder if there is a format conversion with a nil return value. Let me know if more detail is required and I'll see what debug info I can dig up. Thanks for any help!
The text was updated successfully, but these errors were encountered: