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

Assertj-swing stopped working after upgrading to MACOS-X mojave #224

Closed
zolyfarkas opened this issue Oct 5, 2018 · 8 comments
Closed

Assertj-swing stopped working after upgrading to MACOS-X mojave #224

zolyfarkas opened this issue Oct 5, 2018 · 8 comments
Labels

Comments

@zolyfarkas
Copy link

App window shows up, but event simulation does not seem to happen.

Running with Oracle JDK 1.8.0 u181

@croesch croesch added the OS X label Nov 19, 2018
@croesch
Copy link
Collaborator

croesch commented Nov 19, 2018

Hello @zolyfarkas

thanks for opening this short issue. Unfortunately I don't have access to MacOs, so I can't help you with that. But I'm looking forward reviewing and merging your pull requests :)

best regards

@zolyfarkas
Copy link
Author

@croesch if you can give me some tips into where should I look into it would help with coming up with a fix, I am not familiar with the innards of assertj.

let me know.

thank you

@peanball
Copy link

Hi @zolyfarkas,
the issue is with security / privacy settings in MacOS.
Apps that remote control the mouse / keyboard now need to be approved explicitly to avoid malware.

To enable e.g. Eclipse, go to System Preferences > Security & Privacy > Accessibility and add Eclipse to the list of applications on the right.

@smccants
Copy link

Any idea how to do this when the test application is being launched via WebStart?

@peanball
Copy link

Who’s launching it? Do you have a Build Script that ultimately calls javaws? Then you may want to add Terminal.app or whatever you’re using to start it.

@smccants
Copy link

Actually, we are using it in a technical demo. Our salesman launches the demo via downloading a JNLP file and then presses a key which lets the Robot do some things (change the configuration of our system, which we don't want the sales guy to be doing).

@smccants
Copy link

We set the web browser to be an Accessibility application and that fixed the problem. Thanks for your help @peanball !

@zolyfarkas
Copy link
Author

@peanball worked, thanks!

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

No branches or pull requests

4 participants