New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Runkeeper login #185
Comments
android version ? /Jonas On Fri, Feb 6, 2015 at 8:08 AM, mwallgren notifications@github.com wrote:
|
4.2.2 /Markus |
Ok. Some kind of good news here... I've from start used the Google-account to log in to RunKeeper. Never used the mail and password login, and thus think I don't have a password for RunKeeper. As Google-login only led to blank page, I tried the "Forgot password"-link to create new RunKeeper password ("new"... don't think I ever had one.) So. I got a reset-mail, created a password and was able to log in to RunKeeper that way. And - it worked connecting RunnerUp to RunKeeper. I'm very satisfied with that. I just run and log. :-) I hope you coding people can get some useful info out of this. RunnerUp is just superb. Keep up the good work! Thanks!!! |
Still issues connecting properly to RunKeeper. |
RunKeeper feed does not work #234 |
RK login and up/download works fine. |
I was writing in a closed thread #171 on difficulties connecting Runkeeper. I'm now running latest test-version available via Play testarea, but the problem remains.
I have a new Runkeeper account created Jan 31 with Google-account login. Trying to connect from RunnerUp brings up the Runkeeper login-screen. The Google-login button takes me to Google-account login. After typing epost and password and so on the screen goes white and nothing more happens.
I'm not into this stuff very deep, but I think other apps recognises the google accounts already logged into on the android. Isn't that correct? As I have two accounts on the phone I often get the question which one I'd like to use. That's the way the Runkeeper app works if I log in.
I hope my information can be helpful.
The text was updated successfully, but these errors were encountered: