Since the last update, I have been unable to view my charts. I get "The protocol is not supported." Then I get "STRIIV has stopped responding." I have uninstalled, reinstalled, reset my Touch. Still cannot check my charts.
Please send us an email at firstname.lastname@example.org and let us know the email address you use to sign into the Striiv app as well as the operating system on your phone/tablet and we'll help you out.
Striiv Customer Care
I am also having this issue, I have been emailing back and forth with customer service, for over two weeks now with no resolution. :(
Been working on it for about a week, was told "Looks like our app is having issue running on Huawei phones. I've informed our engineering team of this and they'll be looking further into the issue. I'll let you know when I hear any updates from engineering. We appreciate your patience as the issue is diagnosed." Guess I just can't check my charts, but everything else is registering.
Supposedly they are working on it. I was told "Looks like our app is having issue running on Huawei phones. I've informed our engineering team of this and they'll be looking further into the issue. I'll let you know when I hear any updates from engineering. We appreciate your patience as the issue is diagnosed."
Hi - we are working on it! One of the "fun" things about coding for Android is that manufacturers are free to make changes to it, so you get things like Touchwiz on Samsung phones, and MotoBlur on Motorola phones, etc...
What ends up happening is that there are so many different versions of Android running out there that it's well-near impossible to make something that works on every phone running every version of Android guaranteed. We have Huawei (and Xiaomi, and Sony) phones that we're testing on now, so hopefully our Android engineers will have solutions soon!
Hi Theresa, send us an email at email@example.com with your phone model and Android software version included. We'd like to investigate your report in full detail.
Hi Tamsin -- Our engineers are working on a fix for this, but it's something that only happens in Android 4.3. We should have a resolution soon, but if you can update your phone past 4.3 that will take care of it as well!