Repository navigation
Crash in BLETransport APIs when React Native version is 0.81.4 (Recommended by Expo 54) #1310
Description
Prerequisites
- I checked the documentation and FAQ without finding a solution
- I checked to make sure that this issue has not already been filed
Expected Behavior
When React Native is 0.79.6, it works. This bug blocks our upgrade to Expo 54 and RN 0.81.4.
Current Behavior
Crash when calling open and disconnect. Scan works.
Library version
3.4.0, 3.5.0
Device
Android
Environment info
Android, ExpoSteps to reproduce
Use "react-native": "0.81.4"
Formatted code sample or link to a repository
Use this combo, it works, change to 0.81.4, it won't work
"@ledgerhq/hw-app-solana": "7.2.2",
"@ledgerhq/react-native-hw-transport-ble": "6.33.2",
"buffer": "^6.0.3",
"expo": "~54.0.0",
"expo-asset": "~11.1.7",
"expo-status-bar": "~3.0.8",
"react": "19.0.0",
"react-native": "0.79.6", // "0.81.4"
"react-native-ble-plx": "3.4.0",Relevant log output
LOG 🔗 [DEBUG] Attempting TransportBLE.open with device ID: EF:C3:DF:F9:34:21
Parameter specified as non-null is null: method com.facebook.react.bridge.PromiseImpl.reject, parameter code
reject
CharacteristicsForDevice
BlePlxModule.java:527Additional information
No response
Activity
fix: resolve React Native 0.81.4+ compatibility issues
fix: resolve React Native 0.80.0+ compatibility issues
fix: comprehensive React Native 0.80.0+ compatibility fix
sweetbot commentedon Oct 26, 2025
PR for fixing this: #1312
[-]🐛 Android crash in BLETransport APIs when React Native version is 0.81.4 (Recommended by Expo 54)[/-][+]Crash in BLETransport APIs when React Native version is 0.81.4 (Recommended by Expo 54)[/+]fix: comprehensive React Native 0.80.0+ compatibility fix
bjornswift commentedon Nov 1, 2025
Thanks @sweetbot for creating the PR.
@aliberski / @angelos3lex any chance #1312 could be merged in? Looks like that PR solves this issue and issue #1303.
yanascz commentedon Nov 6, 2025
Any guesstimate when this might be fixed and released? 🤔
aliberski commentedon Mar 9, 2026
@sweetbot @bjornswift @yanascz it's fixed in the latest release v3.5.1