Radar Covid Doesn't work about radar-covid-ios HOT 12 CLOSED

I wonder if it's a thing about thresholds, perhaps the contact with the positive was enough for Contact Tracing framework but not for RadarCovid

That's right!. The framework reports a matching key,but you need to have a significant exposure to be reported as high exposure status. You could check the algorithm used for risk calculation and significant exposure here. As you commented, this has to do with the attenuation thresholds (proximity is inferred from signal attenuation) and the accumulated exposure time within these attenuation buckets.
Nevertheless, you get a quite a bit strange behaviour because the alert notification you get (the one with the localization issue) must be fired when the exposure is considered as a significant one and hence the APP status should reflect this.

We will try to reproduce this bug and then provid a fix for that.

Thanks for your support.

from radar-covid-ios.

@pantic79 Great! Any plan to push the changes to the public repo? I think it would be better for the project if the commits were published more frequently so the community could check them before going into a public release.

from radar-covid-ios.

I agree. Our intention is to commit changes to develop branch at least once a week. Unfortunately it couldn't be possible for the moment.

Thanks.

from radar-covid-ios.

Fix Since version 1.1.1
Both problems have been fixed:
1º The notification error has been corrected, collecting the backup that the user makes when consulting the lables service.
f1e86c7

2º Now on the start force the update of the status that DP3T returns.
2bae693

Thanks.

from radar-covid-ios.

Yes, this may be a serious issue, both the localization error and the UI update problem, have you tried force quitting and reopening the app?

// cc. @pantic79 @alopezh

from radar-covid-ios.

Yes, this may be a serious issue, both the localization error and the UI update problem, have you tried force quitting and reopening the app?

// cc. @pantic79 @alopezh

Yes, kill and re-start and 'Sin contactos de riesgo identificados' perhaps if I reinstall it ...

from radar-covid-ios.

@JacoboJesus yes, if you reinstall it, the app should re-download the infected keys, retry the exposure check, find the match and re-alert you.

from radar-covid-ios.

@JacoboJesus yes, if you reinstall it, the app should re-download the infected keys, retry the exposure check, find the match and re-alert you.

Re-installed but still 'Sin contactos de riesgo ...' :(

from radar-covid-ios.

Can you check in the Settings app if there are new exposure checks?

If not, try to force quit and reopen the app, I think doing that after reinstallation forces it to re-download the infected keys (if not it may do it later today).

from radar-covid-ios.

Can you check in the Settings app if there are new exposure checks?

If not, try to force quit and reopen the app, I think doing that after reinstallation forces it to re-download the infected keys (if not it may do it later today).

When I reinstall it, new check and download was made but still the same info.

I wonder if it's a thing about thresholds, perhaps the contact with the positive was enough for Contact Tracing framework but not for RadarCovid

from radar-covid-ios.

When I reinstall it, new check and download was made but still the same info.

Great! 👍🏻

I wonder if it's a thing about thresholds, perhaps the contact with the positive was enough for Contact Tracing framework but not for RadarCovid

Yes, let's wait for the Radar COVID team answer! But at least the notification localization strings should be fixed and if the risk level is lower than the threshold no notification should appear 🤔

from radar-covid-ios.

Just to give you an update. This issue (both problems) has been reproduced and fixed. The fix will be available in the next release that will be uploaded to APP Store by tomorrow if nothing weird happens.

Thanks for your support.

from radar-covid-ios.