Wir3z
Wir3z
> No locations respectively suppression on bad accuracy is per design or per configuration. Reporting location with incorrect data seems counterproductive to me. What this addresses is the ability for...
I'm patiently waiting for this one! I've seen a ton of improvement changes in the commits.
Closing this one. Fixes in the 2.5.x version around the locator + ability for high accuracy on ping mostly fixes/eliminates this need.
Sorry, should have clarified: HTTP I've been testing the PR "status command", and noticed the logs show that the topic is blank for MessageCmd as well. For example, this is...
Ok, I see the issue. The override for HTTP is structured to only check the location message: `override fun onFinalizeMessage(message: MessageBase): MessageBase { // Build pseudo topic based on tid...
I created a PR to add "tid" to the MessageCard. That would restore the behavior 2.4.x had. The current architecture is keying off getContactId() which requires a topic to link...
In order to get cards to work on 2.4.12, I had added a `tid` field to the card JSON payload (fully appreciate that was a deviation from the booklet documentation)....
I ran some additional tests, and without `tid` in the messageCard JSON response, iOS won't display image cards either. As soon as I add that back to the JSON, images...
Since it does currently work on the published iOS and Android versions on HTTP, is there any reason it cannot be documented that it does and add back the changes...
Can you take a look to see if this is an acceptable direction for the PR? Still outstanding: - Unit tests for this commit + changelog update - Connecting this...