[OSX high sierra] Key- press/down/up is only called once #124

Mat-thieu · 2018-11-08T18:26:52Z

Expected Behavior

Upon attaching key- press/down/up, the callback should be fired every time these events happen.

Current Behavior

The callback is only fired once

Possible Solution

No clue

Steps to Reproduce (for bugs)

const iohook = require('iohook');

iohook.on('keydown', event => {
  console.log(event);
});

iohook.start();

Your Environment

NodeJS: 10.11.0

kevinresol · 2018-11-17T12:14:21Z

I can confirm this with node v8.11.4 (no electron)

Djiit · 2018-11-17T18:16:37Z

Hi there !

Thanks for your feedback. I can't reproduce this on Mojave. Will try a bit more tomorrow or later this week when I can.

Mat-thieu · 2018-11-21T11:47:37Z

@Djiit Thanks! Good to know it's working on Mojave at least, it's probably time to update then.
Before I do though, is there anything I can help you with regarding testing on High Sierra? I can place some console logs in the lib and share the results if that helps.

emilevirus · 2018-11-23T14:49:55Z

I'm using only mouse events, but whenever I press a keyboard key, mouse events stop firing. I'm using MacOS High Sierra too.

rinsuki · 2018-11-23T18:32:53Z

me too(in mojave 10.14.1).

my log

$ cat index.js 
const iohook = require("iohook")

iohook.on("keydown", e => {
	console.log("down", e)
})

iohook.on("keyup", e => {
	console.log("up", e)
})

iohook.start(true)
$ node index.js 
hook_run [1121]: Accessibility API is enabled.
hook_run [1172]: CGEventTapCreate Successful.
hook_run [1178]: CFMachPortCreateRunLoopSource successful.
hook_run [1183]: CFRunLoopGetCurrent successful.
hook_run [1196]: CFRunLoopObserverCreate successful.
dispatch_event [108]: Dispatching event type 1.
hook_enable [257]: Thread Result: (0).
process_mouse_moved [882]: Mouse moved to 725, 495.
dispatch_event [108]: Dispatching event type 9.
process_mouse_moved [882]: Mouse moved to 726, 495.
dispatch_event [108]: Dispatching event type 9.
process_mouse_moved [882]: Mouse moved to 728, 496.
dispatch_event [108]: Dispatching event type 9.
process_mouse_moved [882]: Mouse moved to 729, 497.
dispatch_event [108]: Dispatching event type 9.
process_mouse_moved [882]: Mouse moved to 730, 497.
dispatch_event [108]: Dispatching event type 9.
process_mouse_moved [882]: Mouse moved to 730, 497.
dispatch_event [108]: Dispatching event type 9.
process_mouse_moved [882]: Mouse moved to 730, 497.
dispatch_event [108]: Dispatching event type 9.
process_mouse_moved [882]: Mouse moved to 731, 497.
dispatch_event [108]: Dispatching event type 9.
process_key_pressed [367]: Key 0X1E pressed. (0)
dispatch_event [108]: Dispatching event type 4.
process_key_pressed [379]: Using dispatch_sync_f for key typed events.
down { shiftKey: false,
  altKey: false,
  ctrlKey: false,
  metaKey: false,
  keycode: 30,
  rawcode: 0,
  type: 'keydown' }
^C
$ node -v
v8.12.0
$ sw_vers
ProductName:	Mac OS X
ProductVersion:	10.14.1
BuildVersion:	18B75

qbright · 2018-11-27T13:10:02Z

is it fixed?

Djiit · 2018-11-27T13:20:52Z

I can't reproduce this; and I'm on Mojave.

euroclydon37 · 2018-12-26T22:46:56Z

I just ran into this issue on a fresh project identical to the example provided and I'm using Mojave.

Just running in a raw node app, no electron involved. Node v10.10.0

euroclydon37 · 2018-12-31T22:44:19Z

Running in debug mode and found out that it removes all callbacks. I was getting mouse events firing until a key was pressed. So I think this is a problem in the NodeHookAddon.

euroclydon37 · 2018-12-31T22:53:43Z

Does line 89 need a break;? I'm only vaguely familiar with any of the C languages. But if the key is not the escape key, this switch would fall through to the key release case, right?

iohook/libuiohook/src/demo_hook.c

Lines 67 to 89 in 8233c8a

    
           switch (event->type) { 
        
           	case EVENT_KEY_PRESSED: 
        
           		// If the escape key is pressed, naturally terminate the program. 
        
           		if (event->data.keyboard.keycode == VC_ESCAPE) { 
        
           			int status = hook_stop(); 
        
           			switch (status) { 
        
           				// System level errors. 
        
           				case UIOHOOK_ERROR_OUT_OF_MEMORY: 
        
           					logger_proc(LOG_LEVEL_ERROR, "Failed to allocate memory. (%#X)", status); 
        
           					break; 
        
           				case UIOHOOK_ERROR_X_RECORD_GET_CONTEXT: 
        
           					// NOTE This is the only platform specific error that occurs on hook_stop(). 
        
           					logger_proc(LOG_LEVEL_ERROR, "Failed to get XRecord context. (%#X)", status); 
        
           					break; 
        
           				// Default error. 
        
           				case UIOHOOK_FAILURE: 
        
           				default: 
        
           					logger_proc(LOG_LEVEL_ERROR, "An unknown hook error occurred. (%#X)", status); 
        
           					break; 
        
           			} 
        
           		}

LastDreamer · 2019-01-03T17:27:41Z

Hi, i have same issue. After first keydown event callbacks stop calling.

I'm on Mojave 10.14.2, node version 10.15.0.

const ioHook = require('iohook');

ioHook.start(true);

Here is debug output

hook_run [1121]: Accessibility API is enabled.
hook_run [1172]: CGEventTapCreate Successful.
hook_run [1178]: CFMachPortCreateRunLoopSource successful.
hook_run [1183]: CFRunLoopGetCurrent successful.
hook_run [1196]: CFRunLoopObserverCreate successful.
dispatch_event [108]: Dispatching event type 1.
hook_enable [257]: Thread Result: (0).
process_key_pressed [367]: Key 0X39 pressed. (0X31)
dispatch_event [108]: Dispatching event type 4.
process_key_pressed [379]: Using dispatch_sync_f for key typed events.
             ^C

I commented out this line and rebuilt the package.

I don't familiar with C, and don't know what this line does, but now all works fine.

I hoping this may be helpful

Djiit · 2019-01-03T18:03:42Z

Hi guys, These file are part of libuiohook, the lib used by iohook. I suggest you open an issue there. Le jeu. 3 janv. 2019 à 18:27, Oleg Kravchenko <notifications@github.com> a écrit :

…

Hi, i have same issue. After first keydown event callbacks stop calling. I'm on Mojave 10.14.2, node version 10.15.0. const ioHook = require('iohook'); ioHook.start(true); Here is debug output hook_run [1121]: Accessibility API is enabled. hook_run [1172]: CGEventTapCreate Successful. hook_run [1178]: CFMachPortCreateRunLoopSource successful. hook_run [1183]: CFRunLoopGetCurrent successful. hook_run [1196]: CFRunLoopObserverCreate successful. dispatch_event [108]: Dispatching event type 1. hook_enable [257]: Thread Result: (0). process_key_pressed [367]: Key 0X39 pressed. (0X31) dispatch_event [108]: Dispatching event type 4. process_key_pressed [379]: Using dispatch_sync_f for key typed events. ^C I commented out this line <https://github.com/wilix-team/iohook/blob/master/libuiohook/src/darwin/input_hook.c#L380> and rebuilt the package. I don't familiar with C, and don't know what this line does, but now all works fine. I hoping this may be helpful — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#124 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABHZtKo8fbN0NGzFcUVHI4qMogCji2hUks5u_j2NgaJpZM4YVO8m> .

Xen0phobe · 2019-01-28T13:56:31Z

I also have this problem.

I followed LastDreamer's advice and commented-out the offending line. Everything now seems to be working.

random-yang · 2019-02-06T01:52:02Z

Hi, i have same issue. After first keydown event callbacks stop calling.

I'm on Mojave 10.14.2, node version 10.15.0.
const ioHook = require('iohook');

ioHook.start(true);
Here is debug output
hook_run [1121]: Accessibility API is enabled.
hook_run [1172]: CGEventTapCreate Successful.
hook_run [1178]: CFMachPortCreateRunLoopSource successful.
hook_run [1183]: CFRunLoopGetCurrent successful.
hook_run [1196]: CFRunLoopObserverCreate successful.
dispatch_event [108]: Dispatching event type 1.
hook_enable [257]: Thread Result: (0).
process_key_pressed [367]: Key 0X39 pressed. (0X31)
dispatch_event [108]: Dispatching event type 4.
process_key_pressed [379]: Using dispatch_sync_f for key typed events.
             ^C
I commented out this line and rebuilt the package.

I don't familiar with C, and don't know what this line does, but now all works fine.

I hoping this may be helpful

Can you tell me the detail steps to rebuild this?
I comment out this line, and try to rebuild it. But I fail to do this.
Thanks a lot !:>

Karric · 2019-02-06T22:42:58Z

Also having this issue on Mac OS X 10.14.

Karric · 2019-02-08T17:39:56Z

@LastDreamer - Can you provide your steps?

MulverineX · 2019-03-24T19:56:28Z

@Djiit kwhat/libuiohook#2 looks like they were having the issue, but then solved it

Perhaps this was a different issue though

MulverineX · 2019-03-24T19:57:09Z

If it isn't, maybe this module has an outdated version of their code?

Karric · 2019-03-27T14:06:16Z

@MulverineX - That thread is from 2014, I doubt iohook's dependency is that old.

@Djiit - Can you weight in on this?

Djiit · 2019-03-27T14:39:27Z

Hi there !

I can confirm we use libuiohook v1.1 so yes, we have this fix

Karric · 2019-03-27T14:55:59Z

@Djiit - I'm using 'latest: 0.4.0' for iohook, and this 'fires-once' bug still persists on macOS Mojave. Do you have any recommendations? I would very much like to use this package.

MulverineX · 2019-03-27T15:09:14Z

#124 (comment) this comment of any help/work?

strifel · 2019-04-04T18:37:33Z

Just to confirm. Same problem on Mojave here

lymne · 2019-04-18T07:10:31Z

Same problem on Mojave here +1

andrewkuzmych · 2019-05-07T17:41:42Z

on Mojave +1

JoeRandom · 2019-09-28T08:14:45Z

I tried the mentioned workaround but I am somehow not able to compile the build on MacOS 10.14.6 with Node 12.11.

Any other hint on the main issue (#124)?

Scanning dependencies of target uiohook
[ 12%] Building C object CMakeFiles/uiohook.dir/libuiohook/src/darwin/input_helper.c.o
[ 25%] Building C object CMakeFiles/uiohook.dir/libuiohook/src/darwin/input_hook.c.o
/Users/joe/00_code/iohook/libuiohook/src/darwin/input_hook.c:601:32: error: too many arguments to function call, expected 0, have 3
id event_data = objc_msgSend((id) objc_getClass("NSEvent"), sel_registerName("eventWithCGEvent:"), event_ref);
~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/objc/message.h:62:1: note: 'objc_msgSend' declared here
OBJC_EXPORT void
^
/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/objc/objc-api.h:210:25: note: expanded from macro 'OBJC_EXPORT'

define OBJC_EXPORT OBJC_EXTERN OBJC_VISIBLE
                    ^
/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/objc/objc-api.h:199:28: note: expanded from macro 'OBJC_EXTERN'

define OBJC_EXTERN extern
                       ^
/Users/joe/00_code/iohook/libuiohook/src/darwin/input_hook.c:602:36: error: too many arguments to function call, expected 0, have 2
int subtype = (int) objc_msgSend(event_data, sel_registerName("subtype"));
~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/objc/message.h:62:1: note: 'objc_msgSend' declared here
OBJC_EXPORT void
^
/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/objc/objc-api.h:210:25: note: expanded from macro 'OBJC_EXPORT'

define OBJC_EXPORT OBJC_EXTERN OBJC_VISIBLE
                    ^
/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/objc/objc-api.h:199:28: note: expanded from macro 'OBJC_EXTERN'

define OBJC_EXTERN extern
                       ^
/Users/joe/00_code/iohook/libuiohook/src/darwin/input_hook.c:612:34: error: too many arguments to function call, expected 0, have 2
int data = (int) objc_msgSend(event_data, sel_registerName("data1"));
~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/objc/message.h:62:1: note: 'objc_msgSend' declared here
OBJC_EXPORT void
^
/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/objc/objc-api.h:210:25: note: expanded from macro 'OBJC_EXPORT'

define OBJC_EXPORT OBJC_EXTERN OBJC_VISIBLE
                    ^
/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/objc/objc-api.h:199:28: note: expanded from macro 'OBJC_EXTERN'

define OBJC_EXTERN extern
                       ^
/Users/joe/00_code/iohook/libuiohook/src/darwin/input_hook.c:1242:43: error: too many arguments to function call, expected 0, have 2
auto_release_pool = objc_msgSend(pool, sel_registerName("init"));
~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/objc/message.h:62:1: note: 'objc_msgSend' declared here
OBJC_EXPORT void
^
/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/objc/objc-api.h:210:25: note: expanded from macro 'OBJC_EXPORT'

define OBJC_EXPORT OBJC_EXTERN OBJC_VISIBLE
                    ^
/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/objc/objc-api.h:199:28: note: expanded from macro 'OBJC_EXTERN'

define OBJC_EXTERN extern
                       ^
/Users/joe/00_code/iohook/libuiohook/src/darwin/input_hook.c:1251:23: error: too many arguments to function call, expected 0, have 2
objc_msgSend(auto_release_pool, sel_registerName("release"));
~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/objc/message.h:62:1: note: 'objc_msgSend' declared here
OBJC_EXPORT void
^
/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/objc/objc-api.h:210:25: note: expanded from macro 'OBJC_EXPORT'

define OBJC_EXPORT OBJC_EXTERN OBJC_VISIBLE
                    ^
/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/objc/objc-api.h:199:28: note: expanded from macro 'OBJC_EXTERN'

define OBJC_EXTERN extern
                       ^
5 errors generated.
make[2]: *** [CMakeFiles/uiohook.dir/libuiohook/src/darwin/input_hook.c.o] Error 1
make[1]: *** [CMakeFiles/uiohook.dir/all] Error 2
make: *** [all] Error 2
ERR! OMG Process terminated: 2

j0hnm4r5 · 2019-11-19T16:19:00Z

This is still an issue on Catalina 10.15

kubamarkiewicz · 2020-02-29T16:58:48Z

+1 on Mojave

thebigG · 2020-03-02T01:58:39Z

@jsilversun Thanks so much for that fix! I followed all of your steps and I managed to compile iohook from source and got the "iohook.node" compiled library.

However, when I run this
const ioHook = require('./iohook.node'); ioHook.on('mousemove', event => { console.log(event); // { type: 'mousemove', x: 700, y: 400 } }); // Register and start hook ioHook.start();

I get this error:

TypeError: ioHook.on is not a function

Any idea why this is happening?

greggreenhaw · 2020-04-25T16:44:01Z

Why is this not fixed yet? Is the project dead?

thebigG · 2020-04-25T17:22:01Z

Why is this not fixed yet? Is the project dead?

For me the solution was just to compile directly from source directly, not through npm/nodejs or any of that. Just go to https://github.com/kwhat/libuiohook and compile it from source. This nodeJS version is just a wrapper for that one. It's much easier to just compile https://github.com/kwhat/libuiohook directly. After I compiled it from source, not weird bugs have popped in any platform!

greggreenhaw · 2020-04-25T18:12:16Z

Why would they just not fix the real issue

…

On Sat, Apr 25, 2020 at 12:22 PM Lorenzo B Gomez ***@***.***> wrote: Why is this not fixed yet? Is the project dead? For me the solution was just to compile directly from source directly, not through npm/nodejs or any of that. Just go to https://github.com/kwhat/libuiohook and compile it from source. This nodeJS version is just a wrapper for that one. It's much easier to just compile https://github.com/kwhat/libuiohook directly. After I compiled it from source, not weird bugs have popped in any platform! — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#124 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKVYN4PYU3TX6FPZ62OSI3ROML4LANCNFSM4GCU54TA> .

Djiit · 2020-04-25T18:24:25Z

Hey Greg. Thanks for your message. You are free (as in free software) to create a PR with your solution. Any help is greatly appreciated.

…

-- Julien Le sam. 25 avr. 2020 à 20:12, Greg Greenhaw <notifications@github.com> a écrit :

Why would they just not fix the real issue On Sat, Apr 25, 2020 at 12:22 PM Lorenzo B Gomez ***@***.*** > wrote: > Why is this not fixed yet? Is the project dead? > > For me the solution was just to compile directly from source directly, not > through npm/nodejs or any of that. Just go to > https://github.com/kwhat/libuiohook and compile it from source. This > nodeJS version is just a wrapper for that one. It's much easier to just > compile https://github.com/kwhat/libuiohook directly. After I compiled it > from source, not weird bugs have popped in any platform! > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <#124 (comment) >, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AAKVYN4PYU3TX6FPZ62OSI3ROML4LANCNFSM4GCU54TA > > . > — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#124 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAI5TNGYURLHL5INZL2LMILROMRYZANCNFSM4GCU54TA> .

thebigG · 2020-04-25T18:24:39Z

In my case, it wasn't just the solution but it was a much better one. But that's just me. I know some people just want to hook it into NodeJS, but for my case a bearbones C solution was actually better. But again, this was in my specific case. I don't know about anyone else's case. For more context, I used it for this https://github.com/thebigG/Tasker

lorrylockie · 2020-04-27T08:41:45Z

Even though the way JSilversun provides is useful, there's still hope that this problem can be solved.

SimplexShotz · 2020-05-01T15:44:25Z

Hi! I tried the solution explained in this comment #124 (comment) and it works! Thanks @LastDreamer

Not sure when this is going to be fixed but for now our team feels forced to make a fork of iohook until this is fixed, this bug is huge, it makes the library unusable in macOS.

See the steps to fix the library here:

Clone iohook repository
git clone https://github.com/wilix-team/iohook.git iohook

Execute in terminal
cd iohook

Comment this line

Now you need to compile the library

The library used to compile iohook is cmake-js so for example, if you want to build the library for NodeJS v10.16.0 (My case)
You need to execute this:
npx cmake-js compile -r node -v 10.16.0
BTW is useful to use the --help command to see the options of cmake-js like this npx cmake-js compile --help

After the compilation is completed look for the file build/Release/iohook.node, this is your compiled library, now you need to move it to your project. Look in <your_real_project>/node_modules/iohook/builds/ here you need to find the folder according to your platform and node version. For me, the folder name is node-v64-darwin-x64. The v64 is the ABI of the nodeJS version. If you want to find this folder more easily, in the documentation you can find a small script: https://wilix-team.github.io/iohook/manual-build.html

Just copy the script from the docs and run node script.js. The script will tell you the right name folder according to the node version you use to execute the script.

In few words, copy the repo, comment the line, rebuild, copy the compiled library to your real project in the real project and that's it.

Hope this helps you.

I get to the compiling part, and I get this error:

./bootstrap.sh: line 7: autoreconf: command not found
make[2]: *** [CMakeFiles/prepare_iuhook] Error 127
make[1]: *** [CMakeFiles/prepare_iuhook.dir/all] Error 2
make: *** [all] Error 2
ERR! OMG Process terminated: 2

samrae7 · 2020-06-10T07:36:40Z

I also have this issue on Mojave. Will try the workaround provided above. thanks.

samrae7 · 2020-06-11T22:05:38Z

Yup #124 (comment) works for me too. Thanks @LastDreamer

arily · 2020-07-20T08:35:17Z

same here

and I tried to compile myself but not succeed
#include <nan.h>
^~~~~~~
1 error generated.
make[2]: *** [CMakeFiles/iohook.dir/src/iohook.cc.o] Error 1
make[1]: *** [CMakeFiles/iohook.dir/all] Error 2
make: *** [all] Error 2
ERR! OMG Process terminated: 2

can anyone help me?

vamshi-kura · 2020-08-22T16:46:03Z

Hi! I tried the solution explained in this comment #124 (comment) and it works! Thanks @LastDreamer

Not sure when this is going to be fixed but for now our team feels forced to make a fork of iohook until this is fixed, this bug is huge, it makes the library unusable in macOS.

See the steps to fix the library here:

Clone iohook repository
git clone https://github.com/wilix-team/iohook.git iohook

Execute in terminal
cd iohook

Comment this line

Now you need to compile the library

The library used to compile iohook is cmake-js so for example, if you want to build the library for NodeJS v10.16.0 (My case)
You need to execute this:
npx cmake-js compile -r node -v 10.16.0
BTW is useful to use the --help command to see the options of cmake-js like this npx cmake-js compile --help

After the compilation is completed look for the file build/Release/iohook.node, this is your compiled library, now you need to move it to your project. Look in <your_real_project>/node_modules/iohook/builds/ here you need to find the folder according to your platform and node version. For me, the folder name is node-v64-darwin-x64. The v64 is the ABI of the nodeJS version. If you want to find this folder more easily, in the documentation you can find a small script: https://wilix-team.github.io/iohook/manual-build.html

Just copy the script from the docs and run node script.js. The script will tell you the right name folder according to the node version you use to execute the script.

In few words, copy the repo, comment the line, rebuild, copy the compiled library to your real project in the real project and that's it.

Hope this helps you.

@jsilversun
While trying above process I encountered below error.

./bootstrap.sh: line 7: autoreconf: command not found
make[2]: * [CMakeFiles/prepare_iuhook] Error 127
make[1]: * [CMakeFiles/prepare_iuhook.dir/all] Error 2
make: * [all] Error 2

m-thompson-code · 2020-09-20T23:44:00Z

@vamshi-kura I ran into the same issue you did. I had to install some things using brew:

brew install autoconf
brew install automake
brew install libtool
brew install pkg-config

source: kwhat/libuiohook#43 (comment)

Before this I installed cmake-js globally: npm install -g cmake-js (didn't notice until later that cmake-js was a dependency for iohook, so this step might not be needed.

Also I had to install cmake: brew install cmake

As a note, I installed these separately in this order. I don't know if something could go wrong if you install them in a different order or at once.

Another note to add is that I had to run npm install inside iohook to avoid 'nan.h' file not found. @arily

node v10.22.1, npm 6.14.6, macOS Catalina version 10.15.5

tcardlab · 2020-11-23T04:56:00Z

Not sure why this isn't officially fixed. But, just to reiterate:

brew install cmake automake libtool pkg-config autoconf
Also, probably wise to ensure they are up to date. It will tell you and provide the command.
brew upgrade package_name

git clone https://github.com/wilix-team/iohook.git iohook
cd iohook

As mentioned in prior comments, comment out

npm install   
npm install cmake-js  
npx cmake-js compile -r node -v 14.13.0 (whatever version you are using)
npm run build

Note: the jest test doesn't work as it uses a bad path.
Error: Cannot find module '/Users/<username>/Documents/GitHub/iohook/builds/node-v83-darwin-x64/build/Release/iohook.node' from 'index.js'

the last 3 paragraphs here, will tell you where to find and place the newly built package.
Node.js v14.13.0. (Seems to work, but I'll keep you posted)
npm 6.14.8
macOS Mojave version 10.14.6

mac build

$ yarn add or npm install git+https://github.com/tcardlab/iohook.git\#mac-fix

Karric · 2020-12-22T18:32:20Z

@LastDreamer @tcardlab followed your instructions but still not seeing fixed behaviour. Can you not just fork this project with the fixed build?

jangidsh4 · 2021-02-08T15:42:53Z

I am facing same issue on macOS Big Sur 11.1. Keydown/keyup events are called once per app. I tried the suggested fix by commenting line and using the updated iohook.node binary, but still having same issue. Any help would be appreciated.

jangidsh4 · 2021-02-11T18:45:23Z

I am facing same issue on macOS Big Sur 11.1. Keydown/keyup events are called once per app. I tried the suggested fix by commenting line and using the updated iohook.node binary, but still having same issue. Any help would be appreciated.

never mind, I got it working. Well documented steps by #124 (comment), followed the same but it was not working since I just copied "iohook.node" from iohook node_modules after new build by commenting suggested line. You also need to copy "uiohook.dylib" from the same folder into your ./node_modules/iohook/builds/node-v83-darwin-x64/build/release" folder. And it works. Cheers...
node v14.15.3
macOS Big Sur 11.2.1 (updated to the new patch this morning)

ash0x0 · 2021-06-12T01:12:28Z

Is this still an issue with the current version? Someone please indicate so I can get working on this if so.

giladdarshan · 2021-07-01T18:43:40Z

@ash0x0, I've updated my project from using iohook 0.7.2 to 0.9.3 today, issue is still happening if I don't apply the workaround.
Running macOS Mojave, Node v15.11.0.

dasilvacontin · 2024-01-13T13:02:57Z

@ash0x0: Is this still an issue with the current version? Someone please indicate so I can get working on this if so.

Yes, it's still happening.

macOS Ventura 13.4

node v14.21.3

Mat-thieu changed the title ~~[OSX high sierra] Only first key- press/down/up is only returning first event~~ [OSX high sierra] Key- press/down/up is only called once Nov 8, 2018

Djiit added bug An identified bug, though not necessarily being currently investigated mac Mac-related issues labels Nov 17, 2018

Djiit added the help Actively soliciting contributions to help complete this work label Nov 27, 2018

McCraryCharles mentioned this issue Apr 29, 2019

Mouse events not firing after keypres on Mac #163

Open

jangidsh4 mentioned this issue Feb 11, 2021

On macOS big sur 11.1 version, it records keydown only once, keyup not even once. It should record these events on every keyup/keydown. #295

Closed

tcardlab mentioned this issue Feb 15, 2021

Actively Looking For Maintainers ! #291

Open

ash0x0 added awaiting feedback Waiting on an answer or information from issue or PR author to proceed and removed bug An identified bug, though not necessarily being currently investigated labels Jun 12, 2021

ash0x0 self-assigned this Jun 12, 2021

ash0x0 added this to the Todo milestone Jun 15, 2021

brbaird added a commit to brbaird/iohook that referenced this issue Jun 27, 2021

Comment out line 380 as per wilix-team#124 (comment)

960c83d

[OSX high sierra] Key- press/down/up is only called once #124

[OSX high sierra] Key- press/down/up is only called once #124

Comments

Mat-thieu commented Nov 8, 2018 • edited Loading

Expected Behavior

Current Behavior

Possible Solution

Steps to Reproduce (for bugs)

Your Environment

kevinresol commented Nov 17, 2018 • edited Loading

Djiit commented Nov 17, 2018

Mat-thieu commented Nov 21, 2018

emilevirus commented Nov 23, 2018

rinsuki commented Nov 23, 2018

qbright commented Nov 27, 2018

Djiit commented Nov 27, 2018

euroclydon37 commented Dec 26, 2018

euroclydon37 commented Dec 31, 2018 • edited Loading

euroclydon37 commented Dec 31, 2018 • edited Loading

LastDreamer commented Jan 3, 2019

Djiit commented Jan 3, 2019 via email

Xen0phobe commented Jan 28, 2019 • edited Loading

random-yang commented Feb 6, 2019

Karric commented Feb 6, 2019 • edited Loading

Karric commented Feb 8, 2019

MulverineX commented Mar 24, 2019

MulverineX commented Mar 24, 2019

Karric commented Mar 27, 2019

Djiit commented Mar 27, 2019

Karric commented Mar 27, 2019

MulverineX commented Mar 27, 2019

strifel commented Apr 4, 2019

lymne commented Apr 18, 2019

andrewkuzmych commented May 7, 2019

JoeRandom commented Sep 28, 2019 • edited Loading

define OBJC_EXPORT OBJC_EXTERN OBJC_VISIBLE

define OBJC_EXTERN extern

define OBJC_EXPORT OBJC_EXTERN OBJC_VISIBLE

define OBJC_EXTERN extern

define OBJC_EXPORT OBJC_EXTERN OBJC_VISIBLE

define OBJC_EXTERN extern

define OBJC_EXPORT OBJC_EXTERN OBJC_VISIBLE

define OBJC_EXTERN extern

define OBJC_EXPORT OBJC_EXTERN OBJC_VISIBLE

define OBJC_EXTERN extern

j0hnm4r5 commented Nov 19, 2019

kubamarkiewicz commented Feb 29, 2020

thebigG commented Mar 2, 2020

greggreenhaw commented Apr 25, 2020

thebigG commented Apr 25, 2020

greggreenhaw commented Apr 25, 2020 via email

Djiit commented Apr 25, 2020 via email

thebigG commented Apr 25, 2020

lorrylockie commented Apr 27, 2020

SimplexShotz commented May 1, 2020

samrae7 commented Jun 10, 2020

samrae7 commented Jun 11, 2020 • edited Loading

arily commented Jul 20, 2020

vamshi-kura commented Aug 22, 2020 • edited Loading

m-thompson-code commented Sep 20, 2020

tcardlab commented Nov 23, 2020 • edited Loading

Karric commented Dec 22, 2020

jangidsh4 commented Feb 8, 2021

jangidsh4 commented Feb 11, 2021 • edited Loading

ash0x0 commented Jun 12, 2021

giladdarshan commented Jul 1, 2021 • edited Loading

dasilvacontin commented Jan 13, 2024

Mat-thieu commented Nov 8, 2018 •

edited

Loading

kevinresol commented Nov 17, 2018 •

edited

Loading

euroclydon37 commented Dec 31, 2018 •

edited

Loading

euroclydon37 commented Dec 31, 2018 •

edited

Loading

Xen0phobe commented Jan 28, 2019 •

edited

Loading

Karric commented Feb 6, 2019 •

edited

Loading

JoeRandom commented Sep 28, 2019 •

edited

Loading

samrae7 commented Jun 11, 2020 •

edited

Loading

vamshi-kura commented Aug 22, 2020 •

edited

Loading

tcardlab commented Nov 23, 2020 •

edited

Loading

jangidsh4 commented Feb 11, 2021 •

edited

Loading

giladdarshan commented Jul 1, 2021 •

edited

Loading