We're updating the issue view to help you get more done. 

[iOS] [Tidepool Mobile] [Uploader] The background uploader should be able to handle invalid authentication tokens gracefully by notifying the user or by coming to front (if possible) to allow user to login

Description

If a valid login token is not available during background upload attempts, those attempts will fail, but, will be retried every time we get new samples delivered in background from HealthKit. We should either notify the user or have the app come to the foreground to allow the user to login, so that uploads can continue.

It's unclear whether it's worth the extra effort to do this since background token refresh does often work, which should extend the expiration of the token. And when user does bring app to foreground, that should also extend token expiration

Business/Product Success Criteria

None

Done Criteria

None

Design Specifications:

None

Accessibility Specifications

None

Test Strategy

None

Environment

None

New Fields for Analytics/Export Configuration (if needed)

None

Activity

Show:
Janet Diehl
July 29, 2019, 5:25 PM

Janet Diehl moved this card from Maybe Someday to Mobile

Mar 27 at 10:32 AM

MY

Mark Young joined this card

Jan 25, 2018 at 3:22 PM

MY

Mark Young added this card to another board

Sep 21, 2017 at 8:50 AM

Priority

Assignee

Unassigned

QA Assignee

None

Reporter

Janet Diehl

Requested By (External)

None

Fix versions

None

T-Shirt Size

None

Risk Level

None

User Experience Assessment Level

None

UEA: Issue Volume

None

UEA: Category

None

Components

Design Review Required?

None

Design Approved By:

None

QA done during validation of another ticket?

None

Accessibility Review Required?

None

Accessibility Review Approved By

None

Approved for Production By:

None

Marketing Comms

None

Support Follow Up

None

KB Update

None

Resolved Build #

None

Change completion date

None

Pull Request Needed

None

Labels

Configure