There is an incompatible JNA native library installed

[dmilicic]

Version

4.3.1

Summary

This plugin seems to break builds on the latest version, even syncing the project using GraphQL fails.

Steps to reproduce the behavior

Tested on Android Studio Ladybug 2024.2.2 Patch 2 and Meerkat 2024.3.2 Patch 1.
Using java version 23.0.2-zulu community edition.

Steps to reproduce:

1. Open project using GraphQL in Android Studio
2. Download Apollo Kotlin GraphQL plugin 4.3.1
3. Sync project

The same project works on Apollo Kotlin GraphQL plugin 4.2.0

Logs

There is an incompatible JNA native library installed on this system
Expected: 6.1.3
Found:    7.0.0
(at /Applications/Android Studio.app/Contents/lib/jna/aarch64/libjnidispatch.jnilib).
To resolve this issue you may do one of the following:
 - remove or uninstall the offending library
 - set the system property jna.nosys=true
 - set jna.boot.library.path to include the path to the version of the 
   jnidispatch library included with the JNA jar file you are using

[martinbonnin]

Hi 👋 Thanks for sending this! Double checking, this is about the IntelliJ/Android Studio plugin, right? Not the Gradle plugin?

[dmilicic]

Yes, this happens as soon as I installed the IntelliJ/Android Studio plugin. I've also updated the JDK version in the description.

Disabling the plugin clears the issue.

[martinbonnin]

Thanks! We actually just moved the IJ plugin to a separate repo. I'll move the issue there.

[martinbonnin]

Works for me with Android Studio Meerkat Feature Drop | 2024.3.2 Patch 1 and https://github.com/apollographql/apollo-kotlin-tutorial/

Could it be a conflict between different plugins? Can you share your list of installed plugins?

[martinbonnin]

This seems somewhat similar: https://issuetracker.google.com/issues/322622684

Can you try the workaround there in your gradle.properties:

systemProp.jna.boot.library.path=does-not-exist

?

[dmilicic]

I tried setting ones recommended under the Logs section but those didn't work. What worked for me is to use the 4.2.0 version of the plugin.

To be honest, since it currently is working I am hesitant to retry a different workaround as I don't want to end up in problems again, I am writing this for posterity sake :)

If I encounter the issue again I will try the above!

[martinbonnin]

We'll keep this open for a while, see if anyone else bumps into this. Thanks for reporting this!