Page 1 of 1

Error (client) okHit() caught exception:

PostPosted: Sat Jun 17, 2017 8:08 am
by Different Computers
Never seen this before.
Code: Select all
 Error (client)                  okHit() caught exception: NSRangeException -- *** -[__NSArrayM objectAtIndex:]: index 2 beyond bounds [0 .. 1]

Am I right to think this is some sort of timeout in communication between a local LAN mac app and the server?

I was in the midst of creating a new trigger, the app became unresponsive and the log started throwing these.

Re: Error (client) okHit() caught exception

PostPosted: Sat Jun 17, 2017 9:18 am
by matt (support)
I'm not sure. I've never seen that specific error before. It definitely is client specific, but I don't know what caused the client to get in such a state (possibly a client/server communication glitch, server got hung up/busy, or just a client bug). If you see it again or discover steps to reproduce the problem then let us know.

Re: Error (client) okHit() caught exception

PostPosted: Sat Jun 17, 2017 11:25 am
by Different Computers
I think it was happening at a moment where the server was also struggling because it was getting no response from a camera it was trying to serve to a control page being requested by a 3rd device.

Re: Error (client) okHit() caught exception

PostPosted: Fri Dec 02, 2022 4:25 pm
by jay (support)
@Different Computers, did you ever figure out what caused that problem (or how to solve it)? We just had another user report it. We think it's got to be environmental since this is only the second time in 5 years it's been reported...

Re: Error (client) okHit() caught exception

PostPosted: Fri Dec 09, 2022 7:01 am
by Different Computers
I have never seen it regularly enough to track it down. And since 2017 almost everything in my networking environment has changed radically. Truthfully, I don’t even remember what I was doing when this error came up.

Re: Error (client) okHit() caught exception

PostPosted: Sat Dec 10, 2022 5:44 pm
by jay (support)
Thanks. Apparently a reboot solved this user’s issue.