Hi,
is there a specific reason why B4i seems to support natively the MQTT received message retained status (as per this case) while in B4A it looks like (see this other case for example) we need to create a callback with a JavaObject? It would be really handy to have the same information available in B4i in the JMqtt client object. Would it help to create a "wish" case for that? Or maybe there is already one? In that case is there a schedule foreseen ?
thanks!
is there a specific reason why B4i seems to support natively the MQTT received message retained status (as per this case) while in B4A it looks like (see this other case for example) we need to create a callback with a JavaObject? It would be really handy to have the same information available in B4i in the JMqtt client object. Would it help to create a "wish" case for that? Or maybe there is already one? In that case is there a schedule foreseen ?
thanks!
