ConnectivityStatus out of bounds

[matejdro]

Any ideas what that could be caused by?

Caused by: java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
	at io.rebble.libpebblecommon.connection.bt.ble.pebble.ConnectivityStatus.<init>(ConnectivityWatcher.kt:91)
	at io.rebble.libpebblecommon.connection.bt.ble.pebble.ConnectivityWatcher$subscribe$2.invokeSuspend(ConnectivityWatcher.kt:57)

I have managed to trigger it when pairing to a watch. This is with the 8a4a394 lib version.

[matejdro]

This appears to be caused by me forgetting unpair the watch from phone (I only unpaired it on the watch).

Would adding a check for empty data help?

[sjp4]

I've seen this happen for one user, and i'm not sure why. The watch should always return a value in the characteristic. I'm guessing it's a FW bug - is it reproducible for you? Checking for an empty value would leave us not knowing what state the watch is in..

[matejdro]

Tried, but cannot reproduce anymore. I could once with the following steps:

1. Pair the watch to phone A
2. Remove the phone from the watch
3. Remove the phone from Pebble app on the phone A (but not from the bluetooth settings)
4. Pair the watch to the phone B
5. Disconnect from the phone B (but not unpair)
6. Attempt to connect/pair to the phone A