Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

App keeps askig for accessibilityPermission even if accessibilityPermission: false #182

Open
krisdante opened this issue Mar 12, 2024 · 7 comments

Comments

@krisdante
Copy link

const info = await activeWindow({
      accessibilityPermission: false,
      screenRecordingPermission: true,
    });

With this code, for some reason, the Electron app keeps asking for accessibility permission.
It keeps asking, even if both settings are false.

Is this some macOs 14.2.1 (23C71) miss-compatibility?

Why are those flags marked read-only in the interface?

@sindresorhus
Copy link
Owner

Can you confirm you are on version 8.2.1?

@krisdante
Copy link
Author

Yes I am

@sindresorhus
Copy link
Owner

// @kentbetita

@kentbetita
Copy link
Contributor

Hey! Sorry for the delay.

I ca confirm that even when setting accessibilityPermission: false, it is still prompting for accessibility permission when fresh installing active-win.

I've been using the locally compiled mac binary ever since my #180 was merged. I didn't realize it was still causing errors because mine was working fine. I ended up forking the repository and commenting out the code for the accessibility check to confirm that was the issue.

Do you think compiling locally could have played a role in this? My version is running smoothly without any problems.

@SRichner
Copy link

SRichner commented Apr 4, 2024

Having the same issue (also using 8.2.1)

Thank you both very much for another awesome package and your contributions.

@casaout
Copy link

casaout commented Apr 11, 2024

I ca confirm that even when setting accessibilityPermission: false, it is still prompting for accessibility permission when fresh installing active-win.

I can confirm this as well. Thanks for bringing this up; we were quite unsure if we've implemented it wrongly

@SRichner
Copy link

I've been using the locally compiled mac binary ever since my #180 was merged. I didn't realize it was still causing errors because mine was working fine. I ended up forking the repository and commenting out the code for the accessibility check to confirm that was the issue.

Do you think compiling locally could have played a role in this? My version is running smoothly without any problems.

I can confirm that compiling and running active-win locally (macOS Sonoma, Node 18) does not prompt for the accessibility permission (i.e., I set accessibilityPermission: false in the first active-win test case and no prompt is shown, setting it to true shows the prompt).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants