# Critical NullPointerException on BLE Transmit – GATT status 10 & 133 – Application crashes immediately **URL:** \ **Category:** Issues / Bugs\ **Tags:** help\ **Created:** [January 19, 2026, 3:22pm UTC](https://community.thunkable.com/t/critical-nullpointerexception-on-ble-transmit-gatt-status-10-133-application-crashes-immediately/4108263 "2026-01-19T15:22:12Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![mrlynx0730wsur](https://avatars.discourse-cdn.com/v4/letter/m/9de0a6/32.png) [@mrlynx0730wsur](https://community.thunkable.com/u/mrlynx0730wsur)\ **Post date:** [January 19, 2026, 3:22pm UTC](https://community.thunkable.com/t/critical-nullpointerexception-on-ble-transmit-gatt-status-10-133-application-crashes-immediately/4108263/1 "2026-01-19T15:22:12Z")
**Hello everyone,** I am experiencing a critical issue with the Bluetooth Low Energy (BLE) component in Thunkable that is causing my app to crash immediately upon sending commands. Everything was working perfectly a few days ago, but now the app has become completely unstable without any changes to the logic. **The Problem:** When I call the `Transmit Byte Array` block, the application crashes and displays a “Critical Error Occurred” screen. Looking at the detailed Android logs, I see two recurring scenarios: 1. **GATT Status 10 (GATT\_NOT\_FOUND):** The log shows `BleGattCharacteristicException: GATT exception from MAC='XX:XX:XX...', status 10 (GATT_NOT_FOUND), type BleGattOperation{description='CHARACTERISTIC_WRITE'}`. 2. **GATT Status 133:** Occasionally, I get a status 133 error before the crash. 3. **Internal Crash:** Both scenarios lead to a `java.lang.NullPointerException` at `com.facebook.react.bridge.PromiseImpl.reject`. It seems the BLE library fails to handle the GATT error and passes a null parameter, which crashes the React Native bridge. **Technical Details:** - **Hardware:** STM32 microcontroller with an HM-10 (CC2541) Bluetooth module. - **Firmware:** The C code handles UART commands (ASCII ‘C’, ‘6’, ‘X’) and is confirmed working via a PC terminal. - **Thunkable Blocks:** I am using `Connect to Device`, waiting for discovery, and then calling `Transmit Byte Array` using the standard UUID `0000ffe1-0000-1000-8000-00805f9b34fb`. - **Issue:** Even if the device status is “Connected”, the moment I try to write a characteristic, the app terminates. **What I’ve Tried:** - Verified the Characteristic UUID matches the hardware (FFE1). - Added delays (up to 5 seconds) between connection and transmission to allow for Service Discovery. - Cleared Bluetooth cache and restarted the Android device. - Tried removing the “Subscribe” block to minimize GATT operations. Since the hardware logic (RNG, timers, and UART state machine) is fully functional on the microcontroller side, this appears to be a bug in the Thunkable BLE implementation or the underlying `com.polidea.rxandroidble2` library. Has anyone encountered this `PromiseImpl.reject` NullPointerException recently? Is there a workaround to prevent the app from crashing when a GATT error occurs? **Thank you for your help!** ---
**Author:** ![ioannis](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/ioannis/32/146956_2.png) [@ioannis](https://community.thunkable.com/u/ioannis)\ **Post date:** [January 19, 2026, 3:26pm UTC](https://community.thunkable.com/t/critical-nullpointerexception-on-ble-transmit-gatt-status-10-133-application-crashes-immediately/4108263/2 "2026-01-19T15:26:25Z")
Hi @mrlynx0730wsur I have flagged it to our engineering team and will provide an update as soon as possible. Thank you again for alerting us to this issue and for your time and patience while we work to resolve it. ---
**Author:** ![ioannis](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/ioannis/32/146956_2.png) [@ioannis](https://community.thunkable.com/u/ioannis)\ **Post date:** [February 3, 2026, 9:49pm UTC](https://community.thunkable.com/t/critical-nullpointerexception-on-ble-transmit-gatt-status-10-133-application-crashes-immediately/4108263/3 "2026-02-03T21:49:33Z")
Hi @mrlynx0730wsur thank you again for your patience. I would like to let you know that we have now officially released a fix for this bug. Please keep in mind that you may need to do a [hard refresh](https://docs.thunkable.com/getting-started/data-sources/data-sources#hard-refresh-your-browser) of your browser for the changes to take effect in your project. If this issue is present on the [Thunkable Live](https://thunkable.com/mobile) app, you will want to update that through the App Store and/or Google Play Store before any changes will occur. If your [downloaded or published app](https://docs.thunkable.com/publishing-apps/publish) is affected by this bug, you will need to re-download or re-publish your app for these changes to take effect.