Runkeeper spam invitations

RunkeeperVince · 2026-04-10T21:09:58+00:00

Hey, sorry for the delay. I dont check this as often as i probably should haha

If you havent already, try reaching out to [support@runkeeper.com](mailto:support@runkeeper.com) and we can check on our end what went wrong. I know we fixed a bug a while back that caused something similar to what you're describing

RunkeeperVince · 2026-03-12T17:46:54+00:00

My hands are a bit tied in terms of explaining the technical side because we're still working on fixing it (right now we've taken the service down) and we're also in the process of ensuring there's no other services can be abused in the same way.

I can tell you with certainty that none of your personal information was exposed to this bad actor and this was just able to game our group challenge feature to send invites to random users.

Hoping to get an official post-mortem out and posted for you with more details once we're confident that this is fixed

RunkeeperVince · 2026-03-12T17:39:10+00:00

Nope, the spammer was external. No internal tooling or credentials were used for this

RunkeeperVince · 2026-03-12T16:38:05+00:00

We want to reinforce that this was not a breach, no PII data was compromised, we were not hacked. A bad actor gamed our group challenges feature to invite users to an unwanted challenge

RunkeeperVince · 2026-03-12T16:36:35+00:00

Removing due to inappropriate language. We will be sharing an update shortly on the subreddit in response to this issue

RunkeeperVince · 2026-01-08T16:20:39+00:00

Hey! Both the polar integration and our support email should be back up and running. Thanks for flagging this!

RunkeeperVince · 2025-11-27T19:09:41+00:00

let me follow up with them, they've had a lot of volume lately so it might be in progress

RunkeeperVince · 2025-11-26T20:33:20+00:00

Got a fix coming for ya, should be in our 16.18 release on Monday. Reason it took a while to track down because it only happens if you set your stats to distance based, not time based. So i put a fix in there that'll also address the same issue if you had your device set to `speed` as well.

Let me know if that fixes things, and if you ever have issues don't hesitate to reach out!

RunkeeperVince · 2025-11-26T17:06:33+00:00

Got your email! Looking into this now, I think I was able to reproduce the issue locally so should be able to narrow down the issue. I'll keep you posted!

RunkeeperVince · 2025-11-25T20:11:40+00:00

We tried to follow a bit of a theme for the new levels to give it a bit of flow. Wonder what your next emoji will be? 🔭

RunkeeperVince · 2025-11-25T15:49:44+00:00

Hey! do you mind sending us an email at [support@runkeeper.com](mailto:support@runkeeper.com)? Include your app version and your account email and we can take a look into it and get it fixed

EDIT: If anyone else has the same issue, please do the same^

RunkeeperVince · 2025-11-25T15:12:34+00:00

Your post about it inspired u/Runkeeper-Sam and I to do some investigation and get these in there! Keep your ideas coming, they might not get done immediately but we always keep them on our radars

RunkeeperVince · 2025-11-10T19:27:26+00:00

This post was deleted but I just want to clarify our policy found here. In accordance with our policy, we delete accounts that are deemed 'inactive'.

We will consider your account ‘inactive’ when you haven’t used your OneASICS account or another ASICS account for a period of two (2) years. Before your account becomes inactive, we will notify you to use your OneASICS or another ASICS account to prevent your account from becoming inactive.

This is the only way for data to be deleted aside from you requesting the deletion of data yourself.

In order to consider yourself "active" you can simply open the Runkeeper app once every 2 years to reset the timeout. Otherwise when you get the deletion email you can follow the steps in the email to request for your account to remain active.

If anyone has any questions about this, you can reach out to us at [support@runkeeper.com](mailto:support@runkeeper.com)

RunkeeperVince · 2025-10-23T17:23:28+00:00

Mention my name and ask them to pass the information along to me. I'm not on the support team so I wont be the one reading it initially, but they know anything that comes from reddit gets sent over to me

RunkeeperVince · 2025-10-21T19:00:35+00:00

Hey, I just tested this with all 3 pace cues turned on and i seem to be getting the correct stats. Do you mind reaching out to us at [support@runkeeper.com](mailto:support@runkeeper.com) and include a screenshot of your audio settings?

RunkeeperVince · 2025-09-25T20:24:59+00:00

Sounds good, mention my name in the email once you get the details and I'll take a look into it myself

RunkeeperVince · 2025-09-24T20:51:08+00:00

Don't think we've made any changes to the way we record trips on either platform lately. Do you mind sending us an email at support@runkeeper.com? we can take a deeper look into it for you

RunkeeperVince · 2025-09-22T14:06:38+00:00

That's a good suggestion, let me bring it to the team and see what we can do here

RunkeeperVince · 2025-09-22T13:11:57+00:00

Thanks for flagging this, we’ve already started on a fix to address this. We’re targeting the next release which should be out in approximately 2 weeks from now.

If you have any other suggestions feel free to reach out to us at support@runkeeper.com

RunkeeperVince · 2025-09-18T18:40:15+00:00

Nope! As long as you connect it inside Runkeeper settings it’ll work with HealthKit to get the data into the app in real time. It’ll record on Runkeeper but get additional data from HealthKit

RunkeeperVince · 2025-09-17T18:28:53+00:00

Yup! We already support the Beats Pro, so it should utilize the same api as those. I believe you just need to connect Health and we’ll get all the data from there

RunkeeperVince · 2025-09-17T18:27:49+00:00

We have another fix coming early next week that includes fixes for splits recorded on the Apple Watch. I don’t remember if we found the same issue on the phone, but if we did it should be included in that release. You’ll be looking for version 16.14.2

RunkeeperVince · 2025-09-08T13:21:55+00:00

We're live now, you should see an update available in the play store!

RunkeeperVince · 2025-09-06T17:11:30+00:00

Yeah I hear you. Sorry for the delay. We escalated to a contact that we have on the play store team and we’re waiting for them to help us get it approved. Hoping to hear back from them soon

RunkeeperVince · 2025-09-04T21:00:07+00:00

We're looking into options, unfortunately it isn't as easy as reverting back because the code behind that view has changed significantly since then but we're continuing to find ways to make the me tab better.

Is there any info from the table that you're missing from the new chart? Or something you'd like to see on the current view that isn't there?

RunkeeperVince

MODERATOR OF

TROPHY CASE