Vivoactiv HR bug reports

A 10-minute review of the recent bug reports shows the VA-HR being identified in 7 of the 38 (3 of them mine) reports with very little apparent response from the development team.

01-27-2017 Incorrect GPS date on VA-HR (duplicate of 12-20-2016 below)
01-20-2017 Communications.makeWebRequest fails and crashes GCM on iPhone
01-18-2017 Too-long Icon Text is not centered on Vivoactive
01-15-2017 Confirmation Dialog times out on va-hr, not on 230
01-10-2017 Vivoactive Doesn't Save FIT Contributor Lap & Session Properly
01-04-2017 App with Selectables and timer hardly reacting when executed on Vivoactive HR
12-20-2016 Garmin Time Returned on Vivoactive HR

As someone new to the Garmin camp, 6 weeks into porting a major Pebble app to the platform, I'm looking for confirmation that I'm making the right choice.

jim_m_58 over 8 years ago

#3 isn't the va-hr, and the first and last are really the same thing in two different spots. Also, the va-hr is a common devices that developers have, so bugs on that could be a bit more common to report. The Epix, for example has a fair number of bugs, but isn't that widely used, so you don't see as many reports. And for #3, check out Coleman's response at the end. It's something outside of CIQ, and something the platform folks might not change. (it's kind of a minor thing IMHO)

The time involved to get a fix will be longer if the FW and multiple devices is involved. With some devices, new FW only comes out every couple months, and that is based on the platform group and not Connect IQ. If it's a bug in the SDK, it's often just waiting for the next SDK release, and those happen somewhat regularly. All but one on your list have just been reported in the last few weeks, so they really aren't that old.

If you're expecting a one-week turnaround on bug reports, you'll likely not see that, unless the timing is such that it can be fixed quickly right before an update is released.. Also, in many cases like the "Garmin Time" thing, there are workarounds so you can move past the bug and not have to wait for a fix. Same with the timeout for the confirmation dialog.

For me, I'd rather wait a bit longer for a fix than get a bunch of "quick fix/releases" that might break something else.

Alan.raceQs over 8 years ago

I have just added a new bug report: "The GPS time on the VA-HR runs 5% slow."
My question isn't about the speed the bugs get fixed, but about the number of bugs and the speed with which they're acknowledged. (I just received an acknowledgment about the one submitted 6 days ago.)

jim_m_58 over 8 years ago

Ok, 6 days, with two of those days being a weekend, really isn't that bad, as Coleman also has other things to look at/verify-reproduce/submit. Before a ticket is generated, Coleman first verifies it.

he posted today:

Hey Everyone. Thanks for making the connection. Also, sorry for the delay in some of the reports lately. There are a few that we have had some real trouble reproducing. Sometimes that will cause a delay. I've got both of the bugs mentioned filed.

Thanks again,
Coleman

And right now the Garmin module in Connect IQ, doesn't support the "cloneColeman(numberOfTimes)" call! :)