The Chrome (and Safari) actions work by making AppleScript requests.
Chrome’s auto-update mechanism seems to frequently break the AppleScript connections.
Restarting Google Chrome, Keyboard Maestro Engine, or restarting your Mac will usually resolve the broken connection.
Thanks Peter! You are right, that fixed the problem. Here’s another related (i think) issue: Sometimes when i run a jQuery command that works in Chrome’s console but i get this when i run it with KM:
“0:, 1:, 2:, 3:, 4:, 5:, 6:, 7:, context:missing value, length:8, prevObject:0:, context:missing value, length:1, selector:.theSelector”
I edited the italicized text above for confidentiality reasons, but I don’t think it should affect the answer. Let me know if that’s not the case. Any ideas for what could cause this?
tell application "Google Chrome"
if it is running then
tell window 1
if r is missing value then
set r to ""
set r to "Not Running"