search

localcc / hid_listener

Keyboard/Mouse event listener library for flutter
MIT License
9 stars 6 forks source link

[Q] Additional config required for M1 Mac ? #8

Closed prabhuc94 closed 10 months ago

prabhuc94 commented 10 months ago

Facing (registerKeyboardListener() == null) in Mac M1 processor. Any additional installation / config required ?

localcc commented 10 months ago

No further config is required, did you give your app accessibility permissions?

prabhuc94 commented 10 months ago

@localcc Yes, Given Accessibility permissions. But it's Not working in Chip: [Apple M1 Pro] OS: [Ventura 13.5.1]. Working on Chip [Apple M1] OS [Ventura 13.4.1] Screenshot 2023-09-05 at 1 57 46 PM Screenshot 2023-09-05 at 1 58 18 PM

localcc commented 10 months ago

Are you launching the app as a standalone built executable, or using flutter run/your ide debugging tools?

prabhuc94 commented 10 months ago

@localcc I shared as dmg for mac and exe for windows

prabhuc94 commented 10 months ago

@localcc need any specific config for release build?

localcc commented 10 months ago

It should just work ootb, your app has a window right?

prabhuc94 commented 10 months ago

@localcc Yes, But some users says it's not working! on Mac , Is there anything wrong in my code? Screenshot 2023-09-05 at 2 46 33 PM

It should just work ootb, your app has a window right?

localcc commented 10 months ago

There most likely isn't anything wrong with your code, could you check if the example from the repo works for you on m1 pro?

prabhuc94 commented 10 months ago

There most likely isn't anything wrong with your code, could you check if the example from the repo works for you on m1 pro? @localcc Sure, let me check, Is there any other platform i can communicate with you? So it'll helpful for my project help!

localcc commented 10 months ago

The issue was because of app updates while the app was unsigned, which caused it to lose accessibility permissions under the hood, while not doing so in the accessibility ui, this is fixed by revoking and granting the permissions back to the app in the settings ui. For this issue to not appear at all, you need to sign your app with a certificate, and sign all further updates with it too.