1

I am using the following:

  • Android Studio 2.2.2
  • Android Gradle Plugin 2.2.2
  • NDK r12b, r13
  • externalNativeBuild (ndkBuild and cmake)

I have a native JNI .so that statically links roughly two dozen other libraries. The native library exposes a Java API that is, of course, bound to the JNI. I have successfully built this library using both ndkBuild and cmake, as well as both NDK r12b and r13.

I have a test harness project that builds both an Android app module and this native library module.

According to the Android Studio 2.2 docs, using the combination of Android Studio 2.2.2, Gradle 2.2.2 and the new externalNativeBuild mechanism, native debugging is suppose to "just work." I have found, however, that native debugging only works when I set the Build Variant of the library module to "release".

I would expect a release build to be packaged with the debug symbols stripped out, so I am extremely confused. Has anyone else seen this behavior? I don't want to have to use a release variant for debugging, it makes no sense...

bstar55
  • 3,542
  • 3
  • 20
  • 24
  • I had this exact same problem with Studio 1.5 to 2.0, before finding this workaround that still works in 2.2: http://stackoverflow.com/questions/35312743/workaround-to-link-a-shared-library-in-debug-mode-with-android-studio-v2-0-beta - Hopefully this will work for you. – Shlublu Oct 27 '16 at 13:43
  • I have this issue, too. Actually I didn't know that I could debug using release variant.... – Moved Oct 31 '16 at 17:37

0 Answers0