Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Reading the MTU?

See original GitHub issue

Is there currently a way to detect the current MTU? In iOS CBPeripherals have a function called maximumWriteValueLength which can be used for this purpose, but I could not find anything related to that in the documentation.

Issue Analytics

State:
Created 6 years ago
Comments:6 (4 by maintainers)

Top GitHub Comments

3reactions

juhanilammacommented, Oct 27, 2017

To me it looks like:

On 0.6.4 when cancelDeviceConnection() is called on BleModule.java and promise is being resolved successfully: promise.resolve is called by argument “new Device(device, null).toJSObject(null)” => So the given new device object is initialized with null connection.

New device is then called “toJSObject()”, which executes line: “result.putInt(Metadata.MTU, connection.getMtu());”

This causes NPE as the connection is null and connection.getMtu() is called.

Could you please check this if I read the code correctly.

0reactions

Cierpliwycommented, Nov 30, 2017

Closing this issue as changing MTU was implemented and NPE fixed in 0.6.5. Please open another issue for further discussion or just ask us on Gitter.