Native library conflict with libgojni.so when used alongside OpenVPN packages

[shafiquecbl]

When using flutter_v2ray in a project that also includes OpenVPN packages (e.g., openvpn_flutter), the build fails with a native library merge conflict.

Error:

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:mergeDebugNativeLibs'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.MergeNativeLibsTask$MergeNativeLibsTaskWorkAction
   > 2 files found with path 'lib/arm64-v8a/libgojni.so' from inputs:
      - /Users/mshafique/.gradle/caches/transforms-4/ede96f7f4821d5cc7632f07ad28a12bf/transformed/jetified-openvpn_library-b3941ef040/jni/arm64-v8a/libgojni.so
      - /Users/mshafique/.gradle/caches/transforms-4/289c623916b04860255ea99e4a4407d2/transformed/jetified-libv2ray/jni/arm64-v8a/libgojni.so

Root Cause:
Both flutter_v2ray and openvpn_flutter packages bundle the same native library libgojni.so for multiple architectures (arm64-v8a, armeabi-v7a, x86, x86_64). This causes a merge conflict during the Android build process.

Current Workaround:
Using pickFirst in build.gradle to resolve the conflict causes V2Ray initialization to fail silently.

Expected Behavior:
flutter_v2ray should work without native library conflicts when used alongside other VPN protocol packages.

[zikwall]

Just rename .so libs:

vpiLibs/{arch}/libgojni.so‎ renamed to ‎vpnLib/src/main/jniLibs/{arch}/libgojniopenvpn.so‎

[amir-zr]

@shafiquecbl
You’re facing this issue because flutter_v2ray uses an outdated native structure and conflicts with other VPN packages like OpenVPN due to the duplicated libgojni.so.

To solve this cleanly, please use my new package instead:

🔗 GitHub Release (latest & stable)
https://github.com/amir-zr/flutter_v2ray_client/releases/tag/v3.1.0

🔗 Pub.dev Package
https://pub.dev/packages/flutter_v2ray_client

This version does not include libgojni.so, uses a fully rewritten native bridge, and works perfectly alongside OpenVPN, WireGuard, and other VPN protocol packages without any merge conflict.

If you switch to this package, the issue will be completely resolved.