Skip to content

[Issue] WiFi fails to reconnect if it already failed to connect earlier in the same program cycle #52

Closed

Description

@RomanAlexandroff

Summary

If the device fails to fetch exam data because the WiFi access point is unavailable, later retries often keep failing even after the WiFi Access Point (WiFi Router) is back online with a stable internet connection.

Steps to reproduce

  1. Start the device with the WiFi router/hotspot powered off.
  2. Observe the first exam-data fetch fail (expected).
  3. Turn the router/hotspot on and confirm the network has internet access.
  4. Wait for the device’s next exam-fetch retry attempt(s).

Expected

Once the AP is available, a later retry should connect to WiFi and fetch exam data successfully.

Actual

Retries continue to fail after the AP is restored. Behaviour looks as if the device WiFi module remains stuck on the earlier failure and does not recover until a fuller restart of the device.

Notes

  • Reproduced with a mobile 5G WiFi hotspot used as the AP.
  • Failure persists across multiple retry attempts within the same run.
  • Affects not only fetching exams but all WiFi-connection-related activities.
  • Power-cycling the device with the router already on appears to work on first try (suggests a stuck runtime WiFi state rather than wrong credentials).

Activity

  1. linked a pull request that will close this issueimplement fix for the Issue #52 #55on Aug 12, 2026
  2. added a commit that references this issue on Aug 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

bugSomething isn't working

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions