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

[iOS] [Tidepool Mobile] [Uploader] Don't use file based POST for foreground sessions.

Description

Now that we have separate foreground and background upload URLSessions, consider adding support for foreground session to use normal POST requests, rather than file-based POST requests (the latter are required for background sessions).

It's possible that this might be a perf win for foreground uploading for manual sync of all samples and manual sync of last two weeks. (Should measure before/after perf with this change, for some average number of attempts at uploading all historical samples, expecting a perf win, but, not guaranteed. At least it will be less churn on filesystem / flash storage!)

See https://trello.com/c/TG0DBp2w for separate foreground/background sessions

Business/Product Success Criteria

None

Done Criteria

This is done when delivered to QA. Unfortunately it’s difficult for QA to verify, other than regression pass

Design Specifications:

None

Accessibility Specifications

None

Test Strategy

Mobile Framework test for iOS and Android regression

Environment

None

New Fields for Analytics/Export Configuration (if needed)

None

Activity

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

Janet Diehl moved this card from Maybe Someday to Mobile

Mar 27 at 10:32 AM

MY

Mark Young joined this card

Feb 5, 2018 at 11:00 AM

MY

Mark Young added this card to another board

Feb 5, 2018 at 10:58 AM

Mark Young
April 7, 2020, 9:55 PM

This was committed already in

 

Mark Young
April 7, 2020, 9:57 PM

This is in v3.1.2-71200

Becky Cooney
May 6, 2020, 4:08 PM

Full regression testing through Mobile Framework test on build 72500, it has passed qa and is Waiting for Approval

Tapani Otala
May 6, 2020, 4:34 PM

LGTM

Done

Priority

Assignee

Mark Young

QA Assignee

None

Reporter

Janet Diehl

Requested By (External)

None

Fix versions

T-Shirt Size

S: 2-3 days

Risk Level

None

User Experience Assessment Level

None

UEA: Issue Volume

None

UEA: Category

None

Components

Design Review Required?

No

Design Approved By:

None

QA done during validation of another ticket?

No

Accessibility Review Required?

None

Accessibility Review Approved By

None

Approved for Production By:

Tapani

Marketing Comms

No

Support Follow Up

No

KB Update

No

Resolved Build #

None

Change completion date

None

Pull Request Needed

None

Dev Documentation

No

KissMetrics Events Implemented?

No

Data Model Updates Required by Analytics/Export?

No

Labels

Story Points

3

Sprint

None
Configure