deviceID is not properly published

vanitasvitae / Smack

A modular and portable open source XMPP client library written in Java for Android and Java (SE) VMs

https://igniterealtime.org/projects/smack/

Apache License 2.0

16 stars 3 forks source link

Closed vanitasvitae closed 7 years ago

vanitasvitae commented 7 years ago

Not sure, if its an upstream bug in new PubSubManager.getOrCreateNode() by @Flowdalic or if it was introduced when adopting those changes.

Anyway it seams like the ID gets sent to the DeviceList Node, but DeviceList updates still do not contain it afterwards.

Also I have to rewrite deviceID publishing, since at the moment its not really perfect.

vanitasvitae commented 7 years ago

The issue was that the deviceList node contained multiple items and my implementation always returned the first one (index 0).

I fixed it by deleting all Items if there are more than 1 and publishing the latest list.