Run keeper plugin not logging

[dennispipper]

Using the latest version of slogger and the latest runkeeper app for iPhone on iOS 7, it appears that it something isn't working. It ran all Sept and Oct. the plugin no longer logs my runs since Nov 2

[ats]

Do you get any errors when you run Slogger, or if you restrict it to just the Runkeeper plugin using slogger -o runkeeper? Are you running any other plugins, and if so, do they continue to work?

If Slogger is otherwise working, you might check your Runkeeper API key to make sure it didn't expire or get de-authorized for some reason. I'm not aware of anything that would have caused the plugin to stop working (the plugin itself hasn't changed, anyway).

Alan

On Dec 6, 2013, at 6:51 AM, Dennis Pipper [email protected] wrote:

Using the latest version of slogger and the latest runkeeper app for iPhone on iOS 7, it appears that it something isn't working. It ran all Sept and Oct. the plugin no longer logs my runs since Nov 2

— Reply to this email directly or view it on GitHub.

[jgclark]

I've tried to get this plugin working today, and after a bit of a struggle, it's OK.

The info at http://prettygoodhat.com/2013-05-08-Runkeeper_in_Day_One_via_Slogger.html gives you all you need to navigate the OAuth 2.0 system before it will work.

[ats]

The plugin itself doesn't handle obtaining your authorization key, so you need to do that separately. There is a link to some instructions for this in the plugin's header. Once that's inserted to the plugin configuration, it should work --- at least, it remains working fine for me. I'm not aware of updates on the Runkeeper side that would have broken or threaten to break anything.

Alan

On 10 May 2015, at 22:12, jgclark wrote:

I've now looked at the first few pages of the RunKeeper API pages, and I'm no expert in all of this, but it seems that this plugin isn't going to work against the current API. For starters it currently requires OAuth 2.0, and this codebase doesn't mention that at all. Is anyone using this plugin happily still?

---

Reply to this email directly or view it on GitHub: https://github.com/ttscoff/Slogger/issues/228#issuecomment-100767206

[jgclark]

Thank you, Alan. I realised I'd only followed half of the auth instructions, and so then got it working OK. I then deleted this comment, and changed an earlier one to say that it was now fine. I'm sorry that you got this before my updates!

Regards,

-- Jonathan

_____________________________

From: ats [email protected] Sent: Monday, May 11, 2015 14:29 Subject: Re: [Slogger] Run keeper plugin not logging (#228) To: ttscoff/Slogger [email protected] Cc: jgclark [email protected]

The plugin itself doesn't handle obtaining your authorization key, so   

you need to do that separately. There is a link to some instructions for
this in the plugin's header. Once that's inserted to the plugin
configuration, it should work --- at least, it remains working fine for
me. I'm not aware of updates on the Runkeeper side that would have
broken or threaten to break anything.

Alan

On 10 May 2015, at 22:12, jgclark wrote:

I've now looked at the first few pages of the RunKeeper API pages, and
I'm no expert in all of this, but it seems that this plugin isn't
going to work against the current API. For starters it currently
requires OAuth 2.0, and this codebase doesn't mention that at all. Is
anyone using this plugin happily still?

---

Reply to this email directly or view it on GitHub:
https://github.com/ttscoff/Slogger/issues/228#issuecomment-100767206

— Reply to this email directly or view it on GitHub.

[ats]

I can't tell you how long I spent screwing with getting the auth part to work the first time. I've always been able to get oauth sorted out via curl nonsense, but it just wouldn't work for me with Runkeeper, so I built that dumb request form, and that did the trick. It still seems finicky, but seems to have worked for enough other folks. I'm glad you were able to get it up and running, too. Cheers.