If you restore your iPhone from a backup, or if you get a new phone and transfer your data - then the Health sync will not have the correct perms to sync in the background.
Most users are able to do manual syncs, I believe.
Solution: Uninstall and reinstall Tidepool Mobile
Please see Zendesk Support tab for further comments and attachments.
We do not have great stats tracking this in ZD as for the longest I (Nick) thought that this was just how iOS worked. If it is possible to make it so that we maintain perms when restored from a backup/transferred to a new phone that would be a boon.
NOTE: Risk assessment is the risk (probability and severity) of the adverse event occurring, not the probability of the bug occurring. See above for details.
Probability of an adverse event (and one sentence on why)
Severity of the potential adverse event (and one sentence on why)
Risk Level: (see table)
Mitigation Plan: fix this bug
Probability: None - no data, or obviously incomplete data - very unlikely anyone would not notice and try to adjust their treatment
Severity: None - Baseline Risk - Same as not using Tidepool
Risk level: 0
Mitigation Plan: Fix this issue
Reference: Draft Doc:
Severity: Access inhibited
P - # of Prominent Clinic report: (JAEB STUDY)
A - # of distinct Clinician Reports: 0
B - # of distinct User Reports: 4 (+ many more anecdotally)
C - # of discoveries by Tidepool employees (testing, dogfooding, etc):
D - # of occurrences according to logs (Rollbar, Kissmetrics, etc). 0
Issue Volume Index = 7P + 3A + B + C + D = 11
Issue Level: 13
Using the table, enter a numeric value and escalate based upon score.
is there anything else to be done on this ticket?
I think as long as support is aware of the issue and can walk users though resolving it, then it can be closed. Note: there was no done criteria.
New React Native version of the app has been released. This ticket is obsolete and will need to open a new one if this is still an issue on the new app.