Ok I found a solution if anyones interested - JNA expands itself at a runtime and mac labels it a malware, as it should. The solution is to pre-expand JNA, check it into a library bunbdle and set runtime flag where the library location is. took me 8 hours to understand, I thought it was darwin vs 32/64 arch issues
Ok I found a solution if anyones interested - JNA expands itself at a runtime and mac labels it a malware, as it should. The solution is to pre-expand JNA, check it into a library bunbdle and set runtime flag where the library location is. took me 8 hours to understand, I thought it was darwin vs 32/64 arch issues
I started digging and it looks like its a NSObject issue, I believe the code originated from you many years ago
public NativeFileDialog(final String title,
final int mode)
{
super( "NSObject" ); <<--- fails here
* @author shannah
* @see <a
* href="https://developer.apple.com/library/mac/#documentation/Cocoa/Reference/ApplicationKit/Classes/nssavepanel_Class/Reference/Reference.html">NSSavePanel
* Class Reference</a>
Hi Steve - I am trying to follow your steps to replace JavaNativeFoundation and I am running intto this issue:
“jna3247727192307843813.tmp” cannot be opened because the developer cannot be verified.
this can be traced to
and then java.lang.UnsatisfiedLinkError: jna3247727192307843813.tmp' not valid for use in process: library load disallowed by system policy)
Is JNF needs to be signed ?
I run
codesign -vvv --deep --strict "myApp.app" returns:
myApp.app: valid on disk
myApp.app: satisfies its Designated Requirement
Any insight into situation?