Problem with bleClient.RegisterForShorts

Bugs and Other Issues
1

I've had a really strange problem with bleClient.RegisterForShorts. I opened a 6 month old app - already running on my tablet - and recompiled the code and was surprised to find the result didn't run, despite no alterations to the source code. No error messages, but the code hung up and had to be stopped/restarted.

I transferred to using the MIT App Inventor 2 app to load from the website and found there was an error every time I called RegisterForShorts - or any of the other RegisterForxxx functions. Replacing these with calls to the equivalent ReadShorts calls works as expected, so its not the arguments.

The error messages are pretty weird, ending with
caused by java.lang.illegalArgumentException: UUID string too large at java.util.UUID.fromString(UUID.java:299)

Once that message has appeared on my pc, that's the last thing that the app does. It has to be stopped and restarted to get going again.

Has anyone encountered this before and can anyone explain what's altered in the bleClient libray that may have caused it?

2

Here's some guesswork, until you can post the entire error log here ...

  • wrong BLE extension version?
  • Lost Android permissions on reinstall?
  • Android version upgraded?
  • Bluetooth device list changed between installs?
  • TinyDB save of Bluetooth device address lost on reinstall?
3

Some more searching around and I found the cause. In the description of the BlueToothLE extension, I found the following in the description of the latest update.

  • Fix bad UUID causing crashes on Android 14+

I can confirm that the older version does indeed cause crashes and updating fixes them.

1 Like