e-mission/e-mission-data-collection

Use a wrapper class for the activities as well

Closed this issue · 3 comments

We already do this on iOS. On android, we are using gson directly, but the format is internal and is subject to change, and in fact did change when we bumped google play services versions.

it went from agb and agc to what looks like zzaEg and zzaEh, and of course, promptly broke all our formatting.

{u'zzaEg': 3, u'zzaEh': 92, u'mVersionCode': 1}, u'metadata': {u'write_ts': 1455096242, u'time_zone': u'America/Los_Angeles', u'platform': u'android', u'key': u'background/motion_activity', u'read_ts': 0, u'type': u'sensor-data'}}

We will work around this on the server now, but we really need to have a wrapper on the client that uses the public APIs. That will also make it easier to have a visualization of unpushed data on android.

This was only referenced as a potential future cleanup, not actually fixed!

This was only referenced as a potential future cleanup, not actually fixed!

This was only referenced as a potential future cleanup, not actually fixed!