Runkeeper crashes accessing fitbit run

[dtrjones]

Hi all loving the fitbit charge 2. Before I create a mess on the runkeeper forums I'd thought I'd check here.

My GPS runs from fitbit are synced to runkeeper which is great. However while the summary of the run is ok on the runkeeper app accessing any splits / heart rate etc causes the app to show a blank page. I.e. it crashes.

I've searched on here but nothing is really helpful other than to say the sync is bad and both parties blame each other.

I'll be honest with you. Runkeeper is very reliable for running. I trust it more than fitbit which seems a bit flaky. I bought a fitbit to monitor heart rate during runs so my primary reason for owning the device is now making the fitbit redundant.

If anybody knows how to solve this then I'm all ears. I'll post on the runkeeper forums as well so let's see if we can't get this working together!

[Rich_Laue · Accepted solution]

My thought @dtrjones would be to go on the run keeper board and do a search. With many problems the user is not the first to have them and a search could get the answer without asking. 

I've moved your none hardware question to the third party forum. 

[dtrjones]

Thanks Rich. I will definitely look on the runkeeper forums and report back
on this thread.

The intention of the post was to gage the fitbit user experience with
runkeeper which has served me well for many years.

The issue of course could come from either party but ultimately it looks
bad from runkeeper perspective as the consumer if they are either
processing an incomplete message or corrupting the message during the
upload.

Thanks again!
Dave.

[Rich_Laue]

I'm aware that you want feedback from Fitbit users. I don't have any experience here other than to remove the app and install fresh. 

[sfringer]

@dtrjones I just got my Ionic yesterday and connected my Fitbit account to my Runkeeper account (which is several years old with many tracked activities). Today I did my first GPS-tracked activity on the Ionic. It successfully transferred to Runkeeper. Everything looked good on the Runkeeper site. Reading your post, I launched the Runkeeper app on my Android phone and found the activity. Initially it indicated I needed to tap to see the map. I did that and the map displayed. I then tapped Charts and everything loaded as expected (pace, elevation and heartrate). I could tap and drag to various points for specific point details.

So, seems to work fine in my very limited experience.

Scott

[Hawkeye353rd]

How did you connect the Ionic with Runkeeper?  Thought I had done that but apparently not as I have to manually enter my runs.

[Rich_Laue]

@Hawkeye353rd there are instructions here and here. 

[dtrjones]

Thanks @sfringer yes so I hadn't tried the Runkeeper website! Had a look just this second and the information is all there! Great news. I've already sent Runkeeper Support an email to ask about the issues with there dodgy app!

[sfringer]

Glad to have provided some useful insight @dtrjones.

I'm new to the Fitbit side of the world, so I spend more time lurking; feels good to contribute. Again, I'm not seeing an issue in the app or the website for data synced from my Fitbit account.

Hope you get a solution to your issue.

[dtrjones]

Just want to update you all with my issue for Runkeeper crashing accessing fitbit runs on the Android app. I had this reply on 2nd Feb.

"Thanks for reaching out to Runkeeper Support and so sorry for all the trouble!

It sounds like you're running into one of our known issues here at Runkeeper HQ. The team is aware of this problem and we're working on it as we speak!

As soon as we have any new information I'll be sure to update you with either a permanent solution or potential workarounds in the interim.

Best,
Cara"

[sfringer]

Thanks for the update @dtrjones. Based on the response, I guess I need to count myself lucky for not having encountered this yet.

[sfringer]

And now, @dtrjones, I'm encountering the issue you reported. Tapping any of the detail lines within an activity in the Runkeeper app crashes the app.

I've reported it to Runkeeper, so we'll see if they can get a fix implemented.

[dtrjones]

Thanks @sfringer, I told you so!

Sorry to hear that though - it's just an anoying issue. Did you mentioned it worked before? It did appear from my email from Cara that they were actively working on the issue so hopefully fitbit users will get some love real soon. As always I'll update this discussion as soon as I see something.

[Hawkeye353rd]

Color me lucky.  I've been successful running with my Ionic and having those runs sync with Runkeeper without issue.  Though I do find a little variability in the distance (Fitbit showing less distance compared to Runkeeper).

[sfringer]

@Hawkeye353rd everything is syncing just fine. It's only when I access a synced activity on my Android device that the Android app crashes. I can view everything just fine through the web interface - only downside now is that I cannot track my distance impact on my shoes (as that's only settable through the app and not on the web)

[sfringer]

@dtrjones indeed, for about two weeks, it all worked fine. After this morning's run, I went into the Runkeeper app to add the shoes I wore, and as soon as I tapped the Shoes section, the app crashed. Same also happens now when tapping for Charts.

[RobertoME]

Hello there Runkeeper fellows! I was reading your posts regarding the app is crashing when you tried to see your Fitbit runs. In this case from our end we do not have reports of the Fitbit app is failing to send over this data through the integration.

So it would be recommendable to keep in touch with RunKeeper customer support as we do not have access to their data. I have seen some Runkeeper users are able to resolved this issue by reinstalling the app again. However if this is a bug from Runkeeper's end it would be just matter of time for they to resolve this issue.

However keep me posted how it goes, I'll be giving follow up.

[dtrjones]

Thanks Roberto! Yes indeed. Runkeeper have confirmed the issue I had was a known issue and as the run activity information was successfully transfered from Fitbit to the Runkeeper website, then it's a problem specifically with the Runkeeper application.

[RobertoME]

Hi there @dtrjones, thank you for keeping me informed and for sharing with us that this is a know issue from Runkeeper's end.

I'm confident they will address this as soon as possible for the commodity of all users affected by this issue.

I'll be looking forward for any new update. Stick around if you have other questions.