Examine count resets to 0/3 after app data clear; previous state visible only after manual interaction

XMLWordPrintable

    • Type: Bug
    • Resolution: Done
    • Priority: High
    • 2.0
    • Affects Version/s: None
    • None
    • STOP TB Sprint 5

      After submitting the Contact Follow Up form, the Examine count updates correctly (e.g., 1/3 or 2/3) and the TPT Follow Up button becomes visible.

      However, when the app data is cleared and the user logs in again:

      • The same beneficiary shows Examine count as 0/3
      • The previously saved state is not reflected initially
      • Only after clicking the “Examine” button, the correct previous state (1/3, 2/3, etc.) is displayed

      Steps to Reproduce

      1. Login to the application
      2. Select a beneficiary
      3. Fill and submit Contact Follow Up form
      4. Observe Examine count updated (e.g., 1/3 or 2/3) and TPT Follow Up enabled
      5. Clear application data / reinstall app
      6. Login again
      7. Navigate to the same beneficiary

      Actual Result

      • Examine count shows 0/3 after relogin
      • Previous progress is not visible initially
      • Correct data appears only after clicking Examine button

      Expected Result

      • Examine count should persist correctly after relogin
      • Previously submitted follow-up data should be visible immediately on screen load
      • No manual interaction should be required to refresh state

      Attaching screen recording:-
      MicrosoftTeams-video (26).mp4     MicrosoftTeams-video (27).mp4

        1. image-2026-08-17-15-10-44-860.png
          136 kB
          Nidhi Saini
        2. image-2026-08-17-15-10-57-602.png
          107 kB
          Nidhi Saini
        3. MicrosoftTeams-video (26).mp4
          4.08 MB
          Nidhi Saini
        4. MicrosoftTeams-video (27).mp4
          3.14 MB
          Nidhi Saini

              Assignee:
              Nidhi Saini
              Reporter:
              Nidhi Saini
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: