Recently, my Ionic has been crashing one mile into my runs. By crashing, I mean one second I'm tracking all data on my screen, the next it shuts off. The battery is not dying, as after a re-start it turns on again. After speaking with customer service, I was told that the exercise app is crashing, and that this is a known issue (since Oct. 2018), and that engineers are working on it. I was told to manually (!) record my exercise data in the interim n.b. that's why I purchased the fitbit. I asked for a replacement, but they said it was a known issue for ALL ionic and versa units. I asked for a refund, but it was purchased more than 45 days ago, and through a third party via amazon, so it looks like I'm out of luck, stuck with a watch that isn't smart enough to do what it says on the package. If you're reading this and are thinking about purchasing the ionic or versa; don't, go for a Garmin or Polar instead.
Best Answer
Fitbit Product Experts Alumni are retired members of the Fitbit Product Expert Program. Learn more
Hmm? Did not even ask for a replacement in my situation -> they offered one straight away. Maybe the Fitbit policy has changed the past month. So far the replacement has been working ok in all regards -> running old .19 firmware. Am very hesitant to upgrade to 3.0 while the replacement is still working ok.
Tech Support “did not” tell me that this was a known issue at the time. But reading posts here and in the Versa forum -> Fitbit has now identified this as a clear “known issue” they are trying to correct.
Other “known issues” have also been recently identified by Fitbit in these forums. Especially after the 3.0 starting rolling out. Gotta wonder -> Why roll out 100% without fixing known issues?”
Note: There is another thread asking if 3.0 actually solved this specific crashing issue -> but Fitbit has not yet confirmed it actually has. Am waiting for confirmation it has before updating to 3.0 -> plus waiting to hear if the many other update issues noted have been resolved. Some seem to have really big problems after updating to 3.0.
Best Answer