nostr: Can't migrate to nostr-sdk:0.38.0 Kotlin
Describe the bug
I can’t migrate from v0.37.0 to the newest version v0.38.0, because the app will crash with Fatal signal 5 (SIGTRAP), code 128 (SI_KERNEL). Didn’t have this problem with v0.37.0.
Do you know why this is happening?
Build environment
- Library: sdk
- Language: Kotlin
- Language version: v0.38.0
Additional context
Log when I try to run 0.38.0
---------------------------- PROCESS STARTED (4951) for package com.dluvian.voyage.debug ----------------------------
2025-01-02 04:27:41.337 4951-4951 nativeloader com.dluvian.voyage.debug D Configuring clns-7 for other apk /data/app/~~3XBvPlYs4rctgqh0wDkPOQ==/com.dluvian.voyage.debug-13T4q6XYJGkRW8WX8vyevw==/base.apk. target_sdk_version=35, uses_libraries=, library_path=/data/app/~~3XBvPlYs4rctgqh0wDkPOQ==/com.dluvian.voyage.debug-13T4q6XYJGkRW8WX8vyevw==/lib/x86_64:/data/app/~~3XBvPlYs4rctgqh0wDkPOQ==/com.dluvian.voyage.debug-13T4q6XYJGkRW8WX8vyevw==/base.apk!/lib/x86_64, permitted_path=/data:/mnt/expand:/data/user/0/com.dluvian.voyage.debug
2025-01-02 04:27:41.341 4951-4951 CompatChangeReporter com.dluvian.voyage.debug D Compat change id reported: 202956589; UID 10209; state: ENABLED
2025-01-02 04:27:41.387 4951-4951 CompatChangeReporter com.dluvian.voyage.debug D Compat change id reported: 279646685; UID 10209; state: ENABLED
2025-01-02 04:27:41.446 4951-4951 CompatChangeReporter com.dluvian.voyage.debug D Compat change id reported: 309578419; UID 10209; state: ENABLED
2025-01-02 04:27:41.844 4951-4951 nativeloader com.dluvian.voyage.debug D Load /data/app/~~3XBvPlYs4rctgqh0wDkPOQ==/com.dluvian.voyage.debug-13T4q6XYJGkRW8WX8vyevw==/base.apk!/lib/x86_64/libjnidispatch.so using ns clns-7 from class loader (caller=/data/app/~~3XBvPlYs4rctgqh0wDkPOQ==/com.dluvian.voyage.debug-13T4q6XYJGkRW8WX8vyevw==/base.apk!classes19.dex): ok
2025-01-02 04:27:41.876 4951-4951 libc com.dluvian.voyage.debug A Fatal signal 5 (SIGTRAP), code 128 (SI_KERNEL), fault addr 0x0 in tid 4951 (an.voyage.debug), pid 4951 (an.voyage.debug)
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 23 (23 by maintainers)
Commits related to this issue
- ffi: remove `--lzma` option from UPX in build AAR script The `--lzma` flag caused issues on x86/x86_64 architectures during library compression. Ref https://github.com/rust-nostr/nostr/issues/703 S... — committed to rust-nostr/nostr by yukibtc 2 years ago
- ffi: remove `--lzma` option from UPX in build AAR script The `--lzma` flag caused issues on x86/x86_64 architectures during library compression. Ref https://github.com/rust-nostr/nostr/issues/703 S... — committed to rust-nostr/nostr by yukibtc 2 years ago
- ffi: compress only ARM and x86_64 libraries when building the AAR The UPX compression is known to cause issues on `x86` devices for certain Android API levels (e.g., API 30). Since `x86` devices cons... — committed to rust-nostr/nostr by yukibtc 2 years ago
- ffi: compress only ARM and x86_64 libraries when building the AAR The UPX compression is known to cause issues on `x86` devices for certain Android API levels (e.g., API 30). Since `x86` devices cons... — committed to rust-nostr/nostr by yukibtc 2 years ago
- ffi: compress only ARM and x86_64 libraries when building the AAR The UPX compression is known to cause issues on `x86` devices for certain Android API levels (e.g., API 30). Since `x86` devices cons... — committed to rust-nostr/nostr by yukibtc 2 years ago
I’ve just published the v0.38.2
The LMDB is still not fixed
I started using UPX from v0.37 for binary compression. Since the x86/x86_64 aren’t basically used by any real device but mainly by emulators, I can skip the compression for those arch and compress only the ARM ones.
https://web.archive.org/web/20170808222202/http://hwstats.unity3d.com:80/mobile/cpu-android.html
I also had to change
DEFAULT_CLANG_VERSIONfrom 17 to 18 because I had no 17 folder but other than that I only removed the--lzmaflagAnd yes, removing the flag makes it work