Skip to content

[Bug]: Node list omits nodes from downloaded node DB #3898

Description

@Jord-JD

Contact Details

GitHub

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.8 (29319501) google

Affected Android version

16

Affected phone model

Samsung Galaxy S24 FE

Affected node model

Heltec v4 primarily but also Seeed T-1000E

Affected node firmware version

2.7.16.a597230 Alpha and 2.7.15.567b8ea Beta

Steps to reproduce the bug

  1. Connect to a node which triggers a node DB download.
  2. Open the Nodes screen.
  3. Observe that only a subset of nodes appear, even though the downloaded DB contains more entries.

Actual behavior

  • When the app downloads the node DB from the node, the node list screen does not show all nodes. Only nodes that subsequently transmit or otherwise update are visible.
  • This causes the node count to be lower than expected and makes the node list incomplete until additional traffic occurs.
  • It also causes the most recently heard node to often be several minutes or hours ago.

Note that the persistent notification shows the correct number of nodes (roughly reflecting what is shown on the device screen).

It appears that the node details are downloaded from the node, but are not persisted to the node DB.

The issue does not appear to be consistent, but I have heard from a least one other person that this is an issue affecting them on the Google Play version of the Android app.

Expected behavior

Nodes that are downloaded when connecting are correctly populated into the node DB and shown on the node list.

Screenshots/Screen recordings

No response

Relevant log output

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions