You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When launching okta-aws on a Mac with Apple M1 processor (aarch64), it crashes with the following message:
Loading library prism_es2 from resource failed: java.lang.UnsatisfiedLinkError: /Users/victor.babenko/.openjfx/cache/12.0.1/libprism_es2.dylib: dlopen(/Users/victor.babenko/.openjfx/cache/12.0.1/libprism_es2.dylib, 1): no suitable image found. Did find:
/Users/victor.babenko/.openjfx/cache/12.0.1/libprism_es2.dylib: mach-o, but wrong architecture
/Users/victor.babenko/.openjfx/cache/12.0.1/libprism_es2.dylib: mach-o, but wrong architecture
java.lang.UnsatisfiedLinkError: /Users/victor.babenko/.openjfx/cache/12.0.1/libprism_es2.dylib: dlopen(/Users/victor.babenko/.openjfx/cache/12.0.1/libprism_es2.dylib, 1): no suitable image found. Did find:
/Users/victor.babenko/.openjfx/cache/12.0.1/libprism_es2.dylib: mach-o, but wrong architecture
/Users/victor.babenko/.openjfx/cache/12.0.1/libprism_es2.dylib: mach-o, but wrong architecture
To Reproduce
Steps to reproduce the behavior:
Install okta-aws-cli-assume-role on a Mac with Apple M1 CPU
Run okta-aws in command line
See error
Expected behavior
It should run normally.
Additional context
This was fixed in openjfx 16+6 and higher: openjdk/jfx@e1adfa9
Updating to 16 doesn't help, and 17 isn't on maven yet. Specifying latest version of 17+* helps though.
The text was updated successfully, but these errors were encountered:
Describe the bug
When launching
okta-aws
on a Mac with Apple M1 processor (aarch64), it crashes with the following message:To Reproduce
Steps to reproduce the behavior:
okta-aws
in command lineExpected behavior
It should run normally.
Additional context
This was fixed in openjfx 16+6 and higher: openjdk/jfx@e1adfa9
Updating to 16 doesn't help, and 17 isn't on maven yet. Specifying latest version of 17+* helps though.
The text was updated successfully, but these errors were encountered: