search

rokwire / safer-illinois-app

Source code repository of "Safer Illinois" App - the official COVID-19 app of the University of Illinois.
https://safer.illinois.edu/
Apache License 2.0
33 stars 23 forks source link

[BUG] Safer app status is displaying orange for user who already got vaccine #755

Open Priyaravi8 opened 2 years ago

Priyaravi8 commented 2 years ago

Describe the bug User who already took the vaccine with the status Green is showing Orange.

To Reproduce Steps to reproduce the behavior:

Users already have their status - GREEN (Vaccine user)

  1. Install the Safer app
  2. Complete the initial screens and onboarding screens.
  3. Proceed to the Home screen

Actual Result User with the status Green (Vaccine user) is showing Orange

Expected behavior The safer app status should not change without any test result impact.

Smartphone (please complete the following information):

OS: [e.g. iOS and Android] Version [e.g. 2.12.5]

mihail-varbanov commented 2 years ago

Hi @Priyaravi8, could you attach a snapshot/list of your Health History, having the items expanded please?

InnovativeInventor commented 2 years ago

@mihail-varbanov I can fully reproduce this bug. I am fully vaccinated and have tested recently, but the app showed orange for me on initial setup. Additionally, the online boarding pass shows my proper status (green). After setup, "Your COVID-19 Event History" screen is blank (it says "no history"). However, after manually clicking "Request my vaccine and latest test" button inside the history screen, the app behaves as expected (my status becomes green).

I think the issue is that the app is not properly fetching the testing/vaccine data on the setup flow (and it's unclear, from a user's perspective, how to trigger this fetch manually). I agree that this is absolutely a show-stopper. The whole point of the setup flow is to set up the app. I also don't think that https://github.com/rokwire/safer-illinois-app/commit/58020006ef7865383b5a7f4357c64faae764c224 helps this issue at all.

Please note that while I think this may be the same bug as @Priyaravi8 described, it may be a distinct, new bug.

I am on version 2.11.5 of the app, which I believe is the latest version released on the iOS app store.