"UniFFI API checksum mismatch" in LWK bindings on armeabi-v7a

未关闭

#317 创建于 2026年10月19日 3 条评论 0 个 reaction 已指派 1 人在 GitHub 查看

@ardier16 已经在做这个了。

开始于 2026年10月19日。

评估

这个 Issue 还没有评估数据。

描述

bug status: confirmed

Title

Crash at login on 32-bit ARM (armeabi-v7a): "UniFFI API checksum mismatch" in LWK bindings

Summary

The app crashes immediately when logging in (PIN) on a 32-bit ARM device. The crash comes from the LWK UniFFI integrity check failing when LwkNetworkBackend calls lwk.Network.mainnet(). The same wallet type works on a 64-bit (arm64-v8a) device.

This looks like the known gobley 0.3.7 bug on 32-bit ARM Android (gobley/gobley#252). It was fixed in LWK on 2026-10-09 (Blockstream/lwk@22659e7), but that fix is still listed as "Unreleased" in LWK's changelog. Green currently depends on LWK 0.19.0.

Environment

App: Blockstream App (Green), com.greenaddress.greenbits_android_wallet, version [5.7.0] from Play Store
Device: Xiaomi Redmi A1 (MediaTek Helio A22), Android 12 Go edition
ABI: armeabi-v7a (ro.product.cpu.abilist = armeabi-v7a,armeabi
Works on: Xiaomi Redmi 12 (arm64-v8a)

Steps to reproduce

Install the app on a 32-bit ARM (armeabi-v7a) device.
Let the app be AOT-compiled (Play cloud profile at install, or background dexopt).
Open or create a wallet with pin
The app crashes.

Expected

Actual

Fatal crash:

java.lang.ExceptionInInitializerError
  at lwk.UniffiLib.<clinit>
  at lwk.Network$Companion.mainnet
  at com.blockstream.data.backend.lwk.LwkNetworkBackend.<init>
  at com.blockstream.data.gdk.GdkSession.initNetworkBackends
  at com.blockstream.data.gdk.GdkSession.connect
  at com.blockstream.data.gdk.GdkSession.loginWithLoginCredentials
  at com.blockstream.compose.models.login.LoginViewModel$loginWithPinOrMnemonic$1.invokeSuspend
  ...
Caused by: java.lang.RuntimeException: UniFFI API checksum mismatch: try cleaning and rebuilding your project
  at lwk.IntegrityCheckingUniffiLib.uniffiCheckApiChecksums
  at lwk.IntegrityCheckingUniffiLib.<clinit>

Full logcat

--------  5805  5805 E AndroidRuntime: FATAL EXCEPTION: main
--------  5805  5805 E AndroidRuntime: Process: com.greenaddress.greenbits_android_wallet, PID: 5805
--------  5805  5805 E AndroidRuntime: java.lang.ExceptionInInitializerError
--------  5805  5805 E AndroidRuntime:  at lwk.UniffiLib.<clinit>(r8-map-id-eba37adec517341ce9f8432a2a824f7221e62e373e383229433fbb9433ed751f:8)
--------  5805  5805 E AndroidRuntime:  at lwk.Network$Companion$mainnet$$inlined$uniffiRustCall$1.invoke(r8-map-id-eba37adec517341ce9f8432a2a824f7221e62e373e383229433fbb9433ed751f:4)
--------  5805  5805 E AndroidRuntime:  at lwk.Network$Companion$mainnet$$inlined$uniffiRustCall$1.invoke(r8-map-id-eba37adec517341ce9f8432a2a824f7221e62e373e383229433fbb9433ed751f:14)
--------  5805  5805 E AndroidRuntime:  at lwk.UniffiRustCallStatusHelper.withReference$lib(r8-map-id-eba37adec517341ce9f8432a2a824f7221e62e373e383229433fbb9433ed751f:9)
--------  5805  5805 E AndroidRuntime:  at lwk.Network$Companion.mainnet(r8-map-id-eba37adec517341ce9f8432a2a824f7221e62e373e383229433fbb9433ed751f:12)
--------  5805  5805 E AndroidRuntime:  at com.blockstream.data.backend.lwk.LwkNetworkBackend.<init>(r8-map-id-eba37adec517341ce9f8432a2a824f7221e62e373e383229433fbb9433ed751f:40)
--------  5805  5805 E AndroidRuntime:  at com.blockstream.data.gdk.GdkSession.initNetworkBackends(r8-map-id-eba37adec517341ce9f8432a2a824f7221e62e373e383229433fbb9433ed751f:220)
--------  5805  5805 E AndroidRuntime:  at com.blockstream.data.gdk.GdkSession.connect(r8-map-id-eba37adec517341ce9f8432a2a824f7221e62e373e383229433fbb9433ed751f:153)
--------  5805  5805 E AndroidRuntime:  at com.blockstream.data.gdk.GdkSession.loginWithLoginCredentials(r8-map-id-eba37adec517341ce9f8432a2a824f7221e62e373e383229433fbb9433ed751f:27)
--------  5805  5805 E AndroidRuntime:  at com.blockstream.data.gdk.GdkSession.loginWithLoginCredentials$default(r8-map-id-eba37adec517341ce9f8432a2a824f7221e62e373e383229433fbb9433ed751f:113)
--------  5805  5805 E AndroidRuntime:  at com.blockstream.data.gdk.GdkSession.loginWithWallet(r8-map-id-eba37adec517341ce9f8432a2a824f7221e62e373e383229433fbb9433ed751f:94)
--------  5805  5805 E AndroidRuntime:  at com.blockstream.compose.models.login.LoginViewModel$loginWithPinOrMnemonic$1.invokeSuspend(r8-map-id-eba37adec517341ce9f8432a2a824f7221e62e373e383229433fbb9433ed751f:126)
--------  5805  5805 E AndroidRuntime:  at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(r8-map-id-eba37adec517341ce9f8432a2a824f7221e62e373e383229433fbb9433ed751f:11)
--------  5805  5805 E AndroidRuntime:  at kotlinx.coroutines.DispatchedTask.run(r8-map-id-eba37adec517341ce9f8432a2a824f7221e62e373e383229433fbb9433ed751f:127)
--------  5805  5805 E AndroidRuntime:  at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(r8-map-id-eba37adec517341ce9f8432a2a824f7221e62e373e383229433fbb9433ed751f:1)
--------  5805  5805 E AndroidRuntime:  at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(r8-map-id-eba37adec517341ce9f8432a2a824f7221e62e373e383229433fbb9433ed751f:62)
--------  5805  5805 E AndroidRuntime:  at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(r8-map-id-eba37adec517341ce9f8432a2a824f7221e62e373e383229433fbb9433ed751f:29)
--------  5805  5805 E AndroidRuntime:  at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(r8-map-id-eba37adec517341ce9f8432a2a824f7221e62e373e383229433fbb9433ed751f:1)
--------  5805  5805 E AndroidRuntime:  Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [StandaloneCoroutine{Cancelling}@7dbae6d, Dispatchers.Main.immediate]
--------  5805  5805 E AndroidRuntime: Caused by: java.lang.RuntimeException: UniFFI API checksum mismatch: try cleaning and rebuilding your project
--------  5805  5805 E AndroidRuntime:  at ge.g(r8-map-id-eba37adec517341ce9f8432a2a824f7221e62e373e383229433fbb9433ed751f:3)
--------  5805  5805 E AndroidRuntime:  at lwk.IntegrityCheckingUniffiLib.uniffiCheckApiChecksums(r8-map-id-eba37adec517341ce9f8432a2a824f7221e62e373e383229433fbb9433ed751f:992)
--------  5805  5805 E AndroidRuntime:  at lwk.IntegrityCheckingUniffiLib.<clinit>(r8-map-id-eba37adec517341ce9f8432a2a824f7221e62e373e383229433fbb9433ed751f:22)
--------  5805  5805 E AndroidRuntime:  ... 18 more

Analysis

gradle/libs.versions.toml pins blockstream-lwk = "0.19.0".
LWK's Kotlin bindings are generated with gobley 0.3.7. It declares the u16 returns of the uniffi_lwk_checksum_* functions as Short with JNA direct mapping. Rust zero-extends the value. ART's compiled JNI stubs on 32-bit ARM don't re-extend small return values, so after AOT compilation the checksum read on armeabi-v7a is wrong and uniffiCheckApiChecksums throws. arm64 is unaffected.
LWK fixed this by generating the bindings with a patched gobley (lwk@22659e7, upstream PR gobley/gobley#297). The fix is not in 0.19.0 or 0.19.1.
glsdk (Greenlight) uses the same generator and recently added the same workaround in build/.tasks.yml. glsdk 0.3.0 may therefore also be affected on 32-bit ARM, for example in Lightning flows.
Ruled out: duplicate liblwk.so hidden by packaging.jniLibs.pickFirsts("**/*.so"). GDK 0.78.0 ships only libgreen_gdk_java.so and exports no UniFFI or LWK symbols. glsdk ships libglsdk.

Suggested fix

Bump LWK to the first release containing lwk@22659e7, and glsdk to a release built with the patched gobley.
Possible interim mitigation: android:vmSafeMode="true" in the manifest to prevent AOT compilation, at some performance cost. Dropping armeabi-v7a would instead lock out existing 32-bit users.

Verified workaround

Resetting the app to non-AOT code may avoid the crash without touching wallet data:

adb shell cmd package compile -m verify -f com.greenaddress.greenbits_android_wallet

Background dexopt will likely re-compile the app later, bringing the crash back.

主要语言: Kotlin
星标: 274
派生: 111
PR 合并指标: 30 天内没有已合并 PR

环境准备

没有 Dockerfile 或 Docker Compose 文件
没有 Pull Request 模板
阅读贡献指南

从这里开始

先读完整个 Issue，再读项目的贡献指南。
在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
Fork 仓库，在一个分支上完成修改。
提交 Pull Request，并在描述里引用这个 Issue 编号。

Blockstream/green_android 的其他 Issue

[Feature Request] Memory Tagging Extension (MTE) asynchronous mode
未关闭
- 哪里不对？
难度 1/5 1 小时以内新手友好度 88/100

Blockstream/green_android#313 · 2026年9月25日创建
developmentDebug crashes on startup without app_keys.txt (Koin not started)
未关闭
- 哪里不对？
难度 3/5 1-2 天新手友好度 76/100

Blockstream/green_android#315 · 2026年9月26日创建
Built-in Tor leaves webhook and Meld requests on direct network path
未关闭
- 哪里不对？
难度 4/5 3-5 天新手友好度 55/100

Blockstream/green_android#314 · 2026年9月26日创建
Support scanning SeedQR recovery phrases
可能重新可做 @ardier16 于 57 天前认领，目前没有进行中的 PR。未关闭
- 哪里不对？
feature request

Blockstream/green_android#311 · 2 条评论 · 已指派 1 人 · 2026年8月22日创建
UX: Use "Passphrase BIP39" as a universal untranslated label — don't translate it as "contraseña"
可能重新可做 @ardier16 于 57 天前认领，目前没有进行中的 PR。未关闭
- 哪里不对？
enhancement

Blockstream/green_android#310 · 4 条评论 · 已指派 1 人 · 2026年8月21日创建

查看 Blockstream/green_android 的全部 Issue

相似的 Issue

Home: show a "Download a model to get started" card when no model is installed
未关闭
- 哪里不对？
难度 2/5 1-3 小时新手友好度 72/100

getdictus/dictus-android#187 · 2026年10月23日创建

维护者通常 1 天内回复
Follow-up: docs/multiplatform.md lists stale Compose Multiplatform and Gradle versions
未关闭
- 哪里不对？
documentation follow-up

难度 1/5 1 小时以内新手友好度 84/100

yschimke/cadence#388 · 2026年10月23日创建

维护者通常 1 天内回复
Follow-up: run reference-fonts workflow when design-map.json changes
未关闭
- 哪里不对？
follow-up

难度 1/5 1 小时以内新手友好度 83/100

yschimke/meshcore-mobile#586 · 2026年10月23日创建

维护者通常 1 天内回复
Native FileSink.write and FileSource.readAtMostTo throw ArrayIndexOutOfBoundsException for byteCount 0
未关闭
- 哪里不对？
难度 2/5 1-3 小时新手友好度 78/100

Kotlin/kotlinx-io#529 · 2026年10月23日创建
[Bug] 1.9.29: "What to sync" closes the app when scrolling down
未关闭
- 哪里不对？
难度 2/5 1-3 小时新手友好度 70/100

mcnaveen/health-connect-webhook#110 · 2026年10月23日创建

维护者通常 1 天内回复

更多 Kotlin Issue

"UniFFI API checksum mismatch" in LWK bindings on armeabi-v7a

哪里不对？

评估

描述

Title

Summary

Environment

Steps to reproduce

Expected

Actual

Analysis

Suggested fix

Verified workaround

环境准备

从这里开始

Blockstream/green_android 的其他 Issue

哪里不对？

哪里不对？

哪里不对？

哪里不对？

哪里不对？

相似的 Issue

哪里不对？

哪里不对？

哪里不对？

哪里不对？

哪里不对？

把新 issue 发到你的邮箱