Mariah Muscato Oct 22 •
Mariah Muscato Oct 22 •
Hey Everybody! We're going to try something new and keep an updated list for you on known issues with RunKeeper. Take a look back every so often for updates!
- Experiencing PTP (Pocket Track Problems)?
We have some information about this feature at this link http://support.runkeeper.com/entries/29162688-Experiencing-PTP-Pock.... This is a new feature so there are still some adjustments to be made! Make sure not to open the app while you are pocket tracking! That will disrupt the syncing process between your iPhone's M7 and the RunKeeper app.
- Duplicate Null (0.00) activities
Some users have found that when saving a manually inputted activity through their phone the activity will not save but instead a couple activities pop up with the read of 0.00 for data. Try sending this activity again while connected to WiFi and this problem should be avoided. We have the team working on it and hope to resolve the issue soon.
- "Sorry, couldn't connect to RunKeeper" (FIXED- out in next build)
Some users are not able to sync their trips and see above message. This is an issue with 4.2 and will be fixed in 4.3!
Hey Android friends! We have heard some reports of users seeing different time stamps on their activities. For example if you go for a run on a Wednesday morning at 6:30am, the activity might say you ran Thursday night at 8PM. Weird right? We have our best and brightest looking into the issue! In the meantime, head over to RunKeeper.com where you can edit the activity and adjust the timestamp and date!
On those long runs/rides you may notice some of your end splits have disappeared. The team is aware of this issue and we hope to resolve it ASAP. However, they are not actually gone, you can still view all splits on your account at RunKeeper.com!
- Android: Old Plans "completing" new plans
Some users who use the same training plan twice in a row, will sometimes see that their new training plan is being "completed" by their old plan. We know about this bug, and are going to be attempting to fix it. In the meantime, trying a new plan will be the best bet for you until we can get it fixed.
- Droid: "Duplicate" Activities showing up (FIXED- out in next build)
Sometimes when looking at the Activities tab in app, Users will see multiple instances of an activity, and it will continue to duplicate every time they load that page. This can be fixed by logging out and logging back in. If for some reason you do see a duplicate activity online, make sure to save a copy of the GPX by clicking on GPX at the bottom of the activity screen, then delete one of the activities.
- Elite Users - Posts to Facebook will read a shorter distance than your actual trip.
For any Elite user, there is a known issue with Facebook, where after completing your Live tracked activity, it'll revert to a shorter distance as a header. This will not affect your actual activity length, which can be found by clicking through to your profile page.
- Some activity types not available on web (COMING SOON)
This can cause the activity to change when you edit an activity that is synced to the website. We are aware of this and are hard at work to add these not types to the website!
- Re-Posting activities to Facebook doesn't work.
At this time, Facebook doesn't allow us to repost activities once they've been posted and removed by the user. We're working with them to remedy this situation.
- Some activities not associating to Training Plans correctly.
Some users activities aren't sticking to the Training Plans, they've been completed with. We're investigating but this can be fixed by going to the website, and manually associating the activity. For more info: http://support.runkeeper.com/entries/21681651-How-to-associate-an-a...
- Extremely long trips will not post to Facebook
There's an issue on Facebook's end where if a trip is overly long, distance wise, the number of GPS points is too much for Facebook to handle, and they won't post it. This will typically be more common for Cyclists, as they cover longer distances but has been known on occasion to happen to Runners who exceed Marathon length running distances. We're working with Facebook to try and get this fixed, but it is currently a limitation on their end. The current workaround is to turn the Activity Map to "Just Me" before you post it, as then Facebook doesn't have to deal with the GPS points and will just post your data.