Closed wcoder closed 5 months ago
@wcoder I faced a similar issue but with another sign: the subscribeToCharacteristic listener received nothing without Request MTU (when the default MTU size is used). But, when I set the MTU to 247 (I requested 250), the listener began to receive values.
The issue occurs on Android. On iOS all works great for me.
I think the specific subscribeToCharacteristic request requires the relevant MTU size. When the actual MTU size is not relevant to the specific request, the listener receives nothing.
Try to play with MTU size.
I faced the same issue and fortunately I found this topic. Tried requesting MTU and worked!
Make sure to request MTU then use subscribeToCharacteristic
Describe the bug
The
subscribeToCharacteristic
listener can't receive the notifications after MTU was requested.To Reproduce Steps to reproduce the behavior:
connectTo()
/connectToAdvertisingDevice()
requestMtu
returns 498 or Request MTU (498 - the device supports 498) ->requestMtu
returns 498Actual behavior
and nothing
Expected behavior The
subscribeToCharacteristic
listener should receive the notification immediately after subscription.Workaround
The solution that can help resolve this bug on example app project: #773
Smartphone / tablet
Peripheral device