java.lang.NullPointerException

[ildfnkd]

MQTT Rec: ANDROID-ELE-AL00-cd7aff97e9ba3972(2855)

java.lang.NullPointerException

Attempt to invoke virtual method 'long org.eclipse.paho.client.mqttv3.internal.ClientState.getKeepAlive()' on a null object reference
   org.eclipse.paho.client.mqttv3.internal.ClientComms.getKeepAlive(ClientComms.java:656)
   info.mqtt.android.service.ping.AlarmPingSender.start(AlarmPingSender.kt:28)
   org.eclipse.paho.client.mqttv3.internal.ClientState.connected(ClientState.java:1214)
   org.eclipse.paho.client.mqttv3.internal.ClientState.notifyReceivedAck(ClientState.java:1050)
   org.eclipse.paho.client.mqttv3.internal.CommsReceiver.run(CommsReceiver.java:151)
   java.lang.Thread.run(Thread.java:932)

[hannesa2]

too less information

[ildfnkd]

@hannesa2 When I use it for the first time, I occasionally have a problem with the null pointer, or is there a problem with initialization?

[hannesa2]

What's about version name and a running sample (which additional shows the version name) ?

[FJEagle]

Might be same as #433

[HMeckler]

I am having this same issue on android devices OS 30 using: implementation 'com.github.hannesa2:paho.mqtt.android:4.2.4'

[hannesa2]

I am having this same issue on android devices OS 30 using: implementation 'com.github.hannesa2:paho.mqtt.android:4.2.4'

Please give 4.4 a try

[mohammaddvlpr]

this happens for me too and i dont have any scenario.

It may be handled by putting the block inside try catch and return default value (zero) if any exception is thrown(if it's ok, i can create a pull request to just silent it this way)

here's the code that throws exception inside ClientComms class:

public long getKeepAlive() { return this.clientState.getKeepAlive(); }

the lib's version is 3.6.6.

[hannesa2]

Yes, to give me a chance to analyze, please make a pull request which shows me the issue

[mohammaddvlpr]

Unfortunately the exception is thrown in eclipse paho lib in ClientComms class, is there any way to fix that? changing paho lib is risky i think

[hannesa2]

changing paho lib is risky i think

I see it not risky, I see it just as some additional work.

As these guys from https://github.com/eclipse-paho/paho.mqtt.java moving super slow (or event don't want to move) and decline my offer (years ago) to be a maintainer there, I made a fork with CI and use it here #927

When you know what to do, to avoid this issue in my fork, please make a pull request there and I'll merge, create a release and use it here

[hannesa2]

@ildfnkd
@FJEagle
@mohammaddvlpr
@HMeckler
Please use implementation("com.github.hannesa2:paho.mqtt.android:4.6-beta1") and give me feedback.
I will not merge #927 without feedback.