HealthSnapp for Android v.0.2.3.r2 - 23/03/2018

Modified on Tue, 29 May 2018 at 01:13 PM

(Italic items relevant to end users)

New features:

  • VO2 submax test added.

Bug fixes and improvements from v 0.1.10.r2 to v 0.2.3.r2:

  • Imperial Weight should have 1 decimal.
  • Registration process not restored correctly on step 6.
  • App sometimes does not update report filter dates.
  • Calories not displaying the correct value.
  • Cookie policy link not working.
  • Garmin and Striiv data uploads to the same account
  • Keyboard showing when user navigates to Registration Step 3 even though there's no initial keyboard input on that step
  • Having a whitespace in the password for new user passes app's validation but fails on UsersAPI

Known issues:

  • Camera on Hisense L675 Android 6.0 sluggish
  • Visibility on why scanning isn't returning results
  • Unable to connect tracker to App with Huawei
  • Sometimes, the Cloud on Android app doesn't stop flashing
  • Make tracker pairing more robust
  • Data uploads from Striiv tracker to Healthsnap
  • App crash on failed encryption key creation
  • CI setup for LifeQ Explorer app
  • Expand Unit Test suite
  • Remove all remaining legacy code, unused libraries and unused resources
  • Start writing Espresso tests (Automated UI testing for developers)
  • Move all generic util classes and methods to LifeQCommons module
  • Move all duplicate stateless code to Default Interfaces (Java8 feature)
  • Rework field validation in the whole app
  • FW upgrade from 2.5.4 onwards is very unresponsive
  • OTA FW update not showing sync progress if data must be synced before update can begin
  • Date of birth during profile creation not behaving correctly
  • Tracker management screen sometimes gets stuck on "Software transferred successfully" after successful OTA update
  • Update SDP to TrueTime-enabled build
  • Sensor info sampling not initiated when tracker connection timeout
  • Filter out trackers that have users from tracker discovery results
  • Visual update to exercise result screen
  • Check for FW availability on app startup, but only after sync completes
  • Strict mode violation led to app crash

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article