The first positions from LBS causing exception

Hi,
Using watch protocol for example, if the server receives the first position from LBS or WiFi, then it causes an exception as bellow:

2023-02-01 15:33:58  INFO: [Te8aab9c6: watch < 95.12.14.88] 5b33472a383838383838383838382a303134302a5544322c3031303232332c3134333232362c562c35332e3539353130302c4e2c20372e323336303636372c452c322e37382c3136352e332c302e302c372c34302c32312c34302c302c30303030303030302c312c3235352c3236322c332c31353032302c31393434382c3132362c352c54502d4c494e4b5f3046453038342c31303a66653a65643a663a65303a38342c2d37312c465249545a21426f7820373533302041502c32633a39313a61623a35633a64303a38392c2d37392c4449524543542d32322d4850204d313831204c617365724a65742c65653a35633a36383a34653a35653a32322c2d38362c566f6461666f6e6520486f6d6573706f742c33613a33663a62333a32313a61643a39612c2d38382c566f6461666f6e6520486f7473706f742c33613a33663a62333a32313a61643a39632c2d38382c34352e365d
2023-02-01 15:33:58  INFO: [Te8aab9c6] error - NullPointerException
2023-02-01 15:33:58  INFO: [Te8aab9c6] disconnected

The processInvalidPositions is true both for geolocation and geocoder.

Can you enable full stack traces, so we can see the source of the error?

Hi Anton, the full stack trace was a very usefull tool.

I found the problem, I had some custumized code on the test server and it was causing the error.

Thanks for the help!

Next time you should probably mention that you have a customization upfront.

Sure.

As I always test these errors against the original traccar in order to avoid unnecessary forum posts, but this time I missed between jar files.