Request/Response id mismatch - expected id: 1011, received 1010

[rayonx]

On Android Blockstream App, when re-connecting to a Jade via bluetooth, a bad connection during PIN+Passphrase input could trigger this error in loop.

Request/Response id mismatch - expected id: 1011, received 1010
Request/Response id mismatch - expected id: 1012, received 1011
...
Request/Response id mismatch - expected id: 1071, received 1070

bug.mp4

The only way to resolve it via a force kill of the application.

[ardier16]

@rayonx thanks for the detailed report and reproduction video!

A disrupted Bluetooth request can leave the Jade connection one response behind, causing subsequent requests to repeat the ID-mismatch error. Blockstream Android app 5.6.0 does not include a direct fix for this condition, so we’ll keep the issue open.

Could you also confirm your phone model, Android version, Jade model, and Jade firmware version?

[rayonx]

@rayonx thanks for the detailed report and reproduction video!

A disrupted Bluetooth request can leave the Jade connection one response behind, causing subsequent requests to repeat the ID-mismatch error. Blockstream Android app 5.6.0 does not include a direct fix for this condition, so we’ll keep the issue open.

Could you also confirm your phone model, Android version, Jade model, and Jade firmware version?

It is a flagship Sony Xperia, Android 16, Jade Plus with firmware 1.0.40 radio