OwnTracks 2.5 sometimes doesn't get last reported locations on startup

[hastyeagle]

• App build number: 2.5.0
• Android version: GrapheneOS / Android 14 (2024071200)
• Device: Pixel 7a
• Installation source: APK

For some reason on startup of OwnTracks 2.5, the last retained message (last reported location) is not getting pulled from the MQTT server. Attached are two log files, one "good" which is when it was successful in pulling the last retained messages for the two topics I'm subscribed to. The other is the "bad" log which shows the connection to the server being established, but no messages being received.

OwnTracks 2.4 didn't have this issue -- each time I started it I would see the last reported locations of the devices. If I force close owntracks and re-open it, sometimes it will retrieve the last reported locations, and other times it fails. I don't know what changes that makes it start working properly. My location is unavailable (no GPS signal) both during a "good" and "bad" startup, so that doesn't appear to be the problem.

owntracks-log-bad.txt owntracks-log-good.txt

[growse]

Nice report, thanks. Will take a look when I get online later.

[hastyeagle]

After some more testing it does seem related to not having a GPS signal. While traveling it doesn't seem to have an issue getting the last reported locations on startup. It's only happening while I'm at home. Although it does occassionally get the locations on startup even without a GPS signal.