Some users are experiencing issues uploading to Garmin Connect (I know about 15 users, so there are probably more).
Specifically, the app can't log in. It's a problem that I cannot replicate, the app is working just fine on my side, so it may take more than usual to get this fixed (assuming it's not a garmin issue) and your help is welcome.
I've only got one log so far; it seems to indicate (in a cookie) that your requests will be served by a different data center than usual, and then when a login is attempted the app receives a "500 - server error". Not being able to replicate makes it hard to move forward, and it's even unclear how users are selected (as the cookie is sent before the credentials are sent, assuming it's part of the problem). Error reports are coming from different countries, so it's not a regional thing either.
Things you don't need to do:
- clearing data, reinstalling the app, etc.: this won't help, and actually I've never seen a case where this was needed with my app.
- changing password etc., unless you haven't used the app in a long while (then you might be affected by the changes in garmin's policies: see previous posts for details).
- sending me a log of the app reading from the watch. This is not useful as the problem is with garmin connect, not with the watch.
Useful things you can do:
- send me a log of the app logging into garmin connect. To obtain the log:
1) click options in my app
2) enable device diagnostics
3) enable dump diagnostics
4) try to upload to Garmin Connect. After it fails, and you step back from the upload screen, a toast at the bottom of the screen will inform you that a log file has been created (and where). It's usually /mnt/sdcard/log.txt.bin.
5) Please email me that file.
6) After you do that, turn off the diagnostics as it may cause timeouts while reading data from the garmin device.
The file is re-created when you do other stuff, so please follow the procedure above and don't get creative :-) as you may erase the very data that I need.
- if you can think of anything you have recently done on the garmin website (enrolling on some beta feature, etc.) that might have affected your account, let me know. The issue is not in the app. It's the garmin website responding differently to some users.
- if the problem fixes itself (at least one person reported so) please let me know so I do not chase ghosts.
- if you are not overly concerned with your data, or if you have a spare account that is affected, having credentials for an affected account might help. While there is no guarantee that I'll get the same behavior (as the cookie is sent before credentials) it might still help understanding this issue better. Of course I'm not going to erase your data :-), but I'll try to upload some activities for test.
I usually fix issues rather quickly, but the problem here is that the app is working just fine on my accounts / devices, so as I said this may take a while, sorry. Other web apps (strava etc) are not affected.
Specifically, the app can't log in. It's a problem that I cannot replicate, the app is working just fine on my side, so it may take more than usual to get this fixed (assuming it's not a garmin issue) and your help is welcome.
I've only got one log so far; it seems to indicate (in a cookie) that your requests will be served by a different data center than usual, and then when a login is attempted the app receives a "500 - server error". Not being able to replicate makes it hard to move forward, and it's even unclear how users are selected (as the cookie is sent before the credentials are sent, assuming it's part of the problem). Error reports are coming from different countries, so it's not a regional thing either.
Things you don't need to do:
- clearing data, reinstalling the app, etc.: this won't help, and actually I've never seen a case where this was needed with my app.
- changing password etc., unless you haven't used the app in a long while (then you might be affected by the changes in garmin's policies: see previous posts for details).
- sending me a log of the app reading from the watch. This is not useful as the problem is with garmin connect, not with the watch.
Useful things you can do:
- send me a log of the app logging into garmin connect. To obtain the log:
1) click options in my app
2) enable device diagnostics
3) enable dump diagnostics
4) try to upload to Garmin Connect. After it fails, and you step back from the upload screen, a toast at the bottom of the screen will inform you that a log file has been created (and where). It's usually /mnt/sdcard/log.txt.bin.
5) Please email me that file.
6) After you do that, turn off the diagnostics as it may cause timeouts while reading data from the garmin device.
The file is re-created when you do other stuff, so please follow the procedure above and don't get creative :-) as you may erase the very data that I need.
- if you can think of anything you have recently done on the garmin website (enrolling on some beta feature, etc.) that might have affected your account, let me know. The issue is not in the app. It's the garmin website responding differently to some users.
- if the problem fixes itself (at least one person reported so) please let me know so I do not chase ghosts.
- if you are not overly concerned with your data, or if you have a spare account that is affected, having credentials for an affected account might help. While there is no guarantee that I'll get the same behavior (as the cookie is sent before credentials) it might still help understanding this issue better. Of course I'm not going to erase your data :-), but I'll try to upload some activities for test.
I usually fix issues rather quickly, but the problem here is that the app is working just fine on my accounts / devices, so as I said this may take a while, sorry. Other web apps (strava etc) are not affected.
RSS Feed
