Contact Details

No response

Checklist

• I am able to reproduce the bug with the latest version.

• I have updated to the latest Alpha firmware, and am able to reproduce the bug. Many issues are fixed quickly in alpha before the general beta release.

• I made sure that there are no existing OPEN or CLOSED issues which I could contribute my information to.

• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.

• This issue contains only one bug.

• I have read and understood the Contribution Guidelines.

• I agree to follow this project's Code of Conduct

• I actually read this list, and should be taken seriously.

Affected app version

2.7.10 Internal 3

Affected Android version

16

Affected phone model

Pixel 9a

Affected node model

T1000E, RAK4631

Affected node firmware version

2.7.17

Steps to reproduce the bug

1. Be out and about.
2. Perform a trace-route
3. Traceroute is successful.
4. Go home
5. Open the previously done traceroute and view the map of the outgoing and incoming location.

Actual behavior

Notice that now at home the trace shows the locations of where your personal node now is (at home) not from where you were when you performed the trace. This is true for intermediate hops as well, all positions shown are the latest location not the location when the trace took place.

Expected behavior

Location at time of trace sent is retained of personal node performing the trace and intermediate nodes.

Screenshots/Screen recordings

DM'd to @jamesarich for review.

Relevant log output

N/A

Additional information

No response