RunKeeper

Jim Redding May 08 Known Issues

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 Wednesday for updates! 

Week of 5/22/13

iOS Specific:

  • iOS Elite Users - Partial Trip loss when you're tracking a Live activity and your phone crashes.

For our Elite users on iPhone, if your phone or the App crashes in the middle of a Live tracking activity, when you open RunKeeper up again, it'll resume your trip but lose the beginning part of your trip.

  • iOS: Can't edit trips from the phone

Unfortunately there's a bug in the latest build that prevents users from editing their trips in the app. We'll be fixing it for our next build, but in the meanwhile you can edit your activity online at http://runkeeper.com

 

Android Specific:

  • 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. This is purely a graphics thing and the trips can still be selected and completed normally. Viewing them on the web will not result in this happening.

  • Droid: "Duplicate" Activities showing up

Sometimes when looking at the Activities tab in app, Users will see mutiple instances of an activity, and it will continue to duplicate every time they load that page. The actual activity is not duplicating! This can be fixed by logging out and logging back in.

Web/General:

  • 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 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.

  • 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.

  • Web: Garmin Importer always imports activity as activity type listed in device.

For users importing Garmin trips online, all the trips will come in as the type of activity marked in the device. If you're importing a cycling trip, but you wish to have it as a run, selecting run when importing will still import it as a cycling trip. You can fix this by going to Edit after the trip has been imported. 

  • Jawbone:  RunKeeper trips showing up in UTC instead of Local time. 

We're new to Jawbone! Sorry! We're working with Jawbone to fix this one as well.

  • Time Zone Issues

We've noted a few issues with Time Zones and posts being off. We're looking into it.

  • Web: Not saving Preferences

Some users are finding that their Profile info, namely their Location, I am a..., and Skill level information isn't sticking to their profile and is getting cleared every few days.

  • Web: Multiple Feed items for Photos

Some users who take a high amount of pictures during their activities will see multiple Feed items for the one activity. There's only one activity, so don't delete it!! We can not retrieve a trip if you delete it! You can always hide the multiple feed items until one remains.

  • Fitbit: "Not Connected" in Settings page

Some users, when connecting their Fitbit to RunKeeper, it will read "Not Connected" after it's gone through. It has gone through! It's just taking us a little while to refresh our systems to reflect the change, and we're working on it.

  • Web: FitnessFeed Timestamps off

Some users will look at their Feed and see that it's saying 3 hours ago, or Yesterday for activities done longer ago than that. We're looking into it, but it doesn't affect when the activity was actually completed or logged.

  • Web: Private Measurements are Private to everyone! (Even You)

With the new Website redesign, if you have your Body Measurements setting set to "Just Me" unfortunately it makes it too private, and right now you can't see it.  It's still there, and in your stats, and we're working on getting this fixed ASAP.


Week of 5/15/13

  • iOS: Name of Workout Bug. Fixed!
  • Elite Users: Advanced FitnessReports temporarily removed. Fixed!
  • Signing up for Training Plan from Mobile. Fixed!
  • Sync Errors.  Fixed!
  • Web: Strength Training Pages look screwy.  Fixed!

Week of 5/8/13

  • iOS RunKeeper 3.3 Users - Crash on Startup. Fixed!
  • iOS Users - Pebble only displays Miles instead of Kilometers.  Fixed!
  • Web: Race Pages and Profile Page errors. Fixed!

Chas Wagner Apr 23 Knowledgebase / Apps

Current Limitations of RunKeeper and Pebble

  1. iPhone and Android users - Average speed is not available. Therefore, you will  only see average pace. Again, we're looking to add this option to a future build
  2. International version users on metric system - Instead of a decimal or comma when displaying total distance or average pace, you will see a rectangle with a large X in the middle. It looks weird, we know, but should be fixed in a future release.

Connecting RunKeeper and Pebble:

If your Pebble app is up-to-date and your watch is currently connected to your phone, you should be all set!

When your watch is connected to RunKeeper, you should see a 'watch' icon present on the start screen in the upper left hand corner.

Pebble_Screenshot.png

Using Pebble with RunKeeper:

  • You cannot explicitly start or stop an activity from the Pebble watch. Only pause-resume actions are possible.
  • Once you hit Start from the RunKeeper app, the three stats that will appear on the Pebble watch are:
    • Average Pace (average speed is not currently available)
    • Time
    • Distance
  • To pause or resume a workout, click the right-middle button on your Pebble watch (or in the RunKeeper app on your phone).
  • Once you're done with your activity, you must hit the Stop button on the RunKeeper app.

Help! Pebble won't connect to RunKeeper

To connect Pebble and RunKeeper, all of the following must be true:

  • Your Pebble device must be paired, and connected with your phone (you can verify this status in the Pebble app on your phone. For troubleshooting connections, you should refer to Pebble support.
  • You must turn Bluetooth notifications on for your Pebble device
  • You must be using an up-to-date version of the Pebble App and Pebble firmware. You can check for Pebble firmware updates in the Pebble mobile app. You can check for new Pebble mobile apps in the Apple App store, or Google Play. 

Compatibility

iPhone 3GS, 4, 4S, 5 or any iPod Touch with iOS 5 or iOS 6. Android devices running OS 2.3 and up. Works great with Android 4.0 (Ice Cream Sandwich)! Unfortunately, Pebble does not work with Blackberry, Windows Phone 7, or Palm phones at this time.

Purchase

Buy the watch here - http://getpebble.com/

 

Happy Pebbling!

 

Chas Wagner Apr 22 Known Issues

Currently, there's an issue with our iOS app where when you go to sign-up for a Training Plan, you'll receive an "Unrecognized error" message. While the error message is confusing, the good thing is you are already enrolled in the Training Plan.

To access it properly, logout of the app, making sure to take note of your email address from the Settings tab, and simply log back in.

The two places to access the plan are from the Start tab, by hitting the Workout button then Training Plans. Or, from the Activities tab, you'll see one of the planned workouts for sometime in the future.

If you've got any further questions, please let us know.

Jim Redding Mar 27 Announcements

With the release of Android 3.2 and our support of Six new languages in the app, we wanted to provide an update on how we will be handling support for users in these new Languages:

Thank you for taking the time to visit RunKeeper Support. Unfortunately at this time we do not have the capacity to respond in all new languages ​​now available for RunKeeper. If you are having a problem, please send us a message in English. If you do not speak English, please use a translator, such as http://translate.google.com

Obrigado por reservar um tempo para visitar o Suporte do RunKeeper. Infelizmente, neste momento não podemos responder em todos os idiomas novos disponibilizados no RunKeeper. Se você tiver algum problema, nos envie uma mensagem em inglês. Se você não fala inglês, use um tradutor automático, como ohttp://translate.google.com

Merci d'avoir pris le temps de consulter l'assistance RunKeeper. Malheureusement, nous ne sommes actuellement pas en mesure de vous répondre dans les nouvelles langues désormais disponibles sur RunKeeper. Si vous rencontrez un problème, veuillez nous envoyer un message en anglais. Si vous ne parlez pas anglais, utilisez un outil de traduction tel que http://translate.google.com

Vielen Dank, dass du dir die Zeit genommen hast, den RunKeeper-Support zu besuchen. Leider haben wir momentan nicht die Kapazitäten, in allen neuen verfügbaren Sprachen für RunKeeper zu antworten. Wenn du ein Problem hast, kontaktiere uns bitte auf Englisch. Solltest du kein Englisch sprechen, verwende bitte eine Übersetzungsmaschine wie http://translate.google.com

Ti ringraziamo per aver visitato il Supporto di RunKeeper. Purtroppo in questo momento non abbiamo la possibilità di rispondere in tutte le nuove lingue in cui è ora disponibile RunKeeper. In caso di problemi, mandaci un messaggio in inglese. Se non parli inglese, utilizza un traduttore, come http://translate.google.com

RunKeeper サポートをご覧いただき、ありがとうございます。申し訳ございませんが、現在、RunKeeper で新しく対応可能になった言語でのサポートはご利用いただけません。お困りの際は英語でお問い合わせください。英語以外の言語を話される方は、翻訳ツール(http://translate.google.comなど)をご利用ください。

Gracias por tomarte el tiempo de visitar Ayuda de RunKeeper. Lamentablemente en este momento no podemos responder en todos los nuevos idiomas disponibles para RunKeeper. Si tiene un problema, envíenos un mensaje en inglés. Si no habla inglés, use un traductor, como http://translate.google.com

 

Overview | Recent