fix: native code abort signal crash

Author: ovitrif

Justfile

@@ -137,7 +137,12 @@ build task="assembleDevDebug":
     {{ gradle }} {{ task }}
 
 release:
+    #!/usr/bin/env sh
+    set -eu
     {{ gradle }} assembleMainnetRelease bundleMainnetRelease
+    symbols="app/build/outputs/native-debug-symbols/mainnetRelease/native-debug-symbols.zip"
+    test -f "$symbols"
+    ls -lh "$symbols"
 
 install:
     {{ gradle }} installDevDebug

app/build.gradle.kts

@@ -230,6 +230,7 @@ android {
             )
             signingConfig = signingConfigs.getByName("release")
             ndk {
+                debugSymbolLevel = "FULL"
                 // noinspection ChromeOsAbiSupport
                 abiFilters += listOf("armeabi-v7a", "arm64-v8a")
             }

app/src/test/java/to/bitkit/build/NativeReleaseConfigTest.kt

@@ -0,0 +1,37 @@
+package to.bitkit.build
+
+import kotlin.io.path.Path
+import kotlin.io.path.exists
+import kotlin.io.path.readText
+import kotlin.test.Test
+import kotlin.test.assertTrue
+
+class NativeReleaseConfigTest {
+
+    private val repoRoot = generateSequence(
+        Path(requireNotNull(System.getProperty("user.dir")) { "user.dir is required" }),
+    ) { it.parent }
+        .first { it.resolve("gradle/libs.versions.toml").exists() }
+
+    @Test
+    fun `release build keeps full native debug symbols`() {
+        val buildFile = repoRoot.resolve("app/build.gradle.kts").readText()
+
+        assertTrue(
+            buildFile.contains("""debugSymbolLevel = "FULL""""),
+            "Release builds must keep full native debug symbols for Play crash symbolication.",
+        )
+    }
+
+    @Test
+    fun `release recipe verifies native debug symbols archive`() {
+        val justfile = repoRoot.resolve("Justfile").readText()
+
+        assertTrue(
+            justfile.contains(
+                """symbols="app/build/outputs/native-debug-symbols/mainnetRelease/native-debug-symbols.zip"""",
+            ),
+            "Release builds must verify the native debug symbols archive before publishing.",
+        )
+    }
+}

docs/issue-982-native-sigabrt.md

@@ -0,0 +1,32 @@
+# Issue 982 Native SIGABRT
+
+## Summary
+
+Google Play reported production SIGABRT crashes for mainnet build 181 / 2.2.0. Play showed raw native program-counter addresses in `split_config.arm64_v8a.apk` instead of resolving them to library functions.
+
+Android Studio Quail 2 was running locally, but the available `android studio` CLI/MCP commands only exposed Studio status, source navigation, file analysis, Compose preview rendering, and version lookup. No App Quality Insights or Android Vitals retrieval command was available, so the GitHub issue's Play Vitals details were used as the machine-readable crash source.
+
+## Symbolication
+
+Exact release context:
+
+- tag: `v2.2.0`
+- version code: `181`
+- native deps: `bitkit-core-android 0.1.56`, `ldk-node-android 0.7.0-rc.36`
+- rebuilt temp worktree: `/tmp/bitkit-android-v2.2.0-symbols`
+
+The historical release build completed through native library extraction and failed only at final bundle signing in the temporary worktree. The generated intermediary AAB was converted to APK splits with bundletool, then the arm64 split was inspected.
+
+Reproduction used a detached `v2.2.0` worktree at the temp path above, authenticated GitHub Packages through `gh auth token`, built the `mainnetRelease` bundle task until native extraction completed, converted the intermediary AAB to APK splits with bundletool `1.18.1`, and inspected `/tmp/bitkit-v2.2.0-apks/splits/base-arm64_v8a.apk`.
+
+The crash addresses resolve directly as library-relative addresses in `libbitkitcore.so`. Running `llvm-addr2line` against `libbitkitcore.so` maps frames into bitkit-core Rust code and dependencies such as `btleplug`, `bdk`, `rusqlite`, and `tokio`. Running the same addresses against `libldk_node.so` produced no matching symbol names.
+
+The direct addresses are executable addresses in the `libbitkitcore.so` ELF. Subtracting the APK ZIP data offset maps the addresses into non-executable sections such as rodata/exception tables, so the direct address form is the usable symbolication path.
+
+Conclusion: issue #982 is a bitkit-core native crash cluster, not an LDK-node crash cluster.
+
+## Fix
+
+Current `master` already consumes `bitkit-core-android 0.1.64`, moving production off the `0.1.56` artifact used by v2.2.0 build 181. A later `0.1.66` artifact was reviewed, but its release notes and commit range focus on the new on-chain watcher and do not provide evidence for this SIGABRT cluster. This branch therefore does not carry an unrelated `bitkit-core` bump.
+
+Release builds also explicitly request full native debug symbols and the `just release` recipe verifies that `app/build/outputs/native-debug-symbols/mainnetRelease/native-debug-symbols.zip` exists after building.