A few weeks ago the guys at Strava made some changes to their authentication API and they broke my app. Unfortunately, I won't be upgrading the app soon (see below). However, there is an easy workaround. It's the same procedure you would have to go through if you give up on my app and buy a new garmin, so you may want to hold onto your money anyway : ).

Strava can auto-synch with garmin connect, which is free. So the steps are:

1) create an account with garmin connect, if you don't have one already.
2) test that garmin connect works fine with my app. There are currently no known issues here.
3) log into strava, go to settings, then choose "my apps" (it used to be "third party apps") and enable synchronization with garmin connect.

That's it. Upload to garmin connect from my app, and your activities will show up in strava. In my testing, it was pretty much immediate, but as usual with these things, there might be a small lag.

As I mentioned, if you buy a new garmin and get one that is designed to be used with a smartphone, it will only talk to the garmin connect app, so to get your stuff into strava you'll have to go through the above anyway. 

Back on the sad news: the reason I'm not fixing the app right now is that 1) the app has never really been profitable, but it has plummeted to pretty much nothing in the past couple of years, as people choose to move to newer garmin models. It's hard to pour time into something that earns nothing. 2) I can't simply change the authentication code and push the new app to google play. Google now wants all apps to target android 9, and that requires sizeable changes into many areas. Due to (1), I really can't do it now. In the future, I may have to publish an APK that you'll have to sideload.

Bottom line: there is an easy workaround, please use that and enjoy your old garmin for a while longer : )

If you're having troubles uploading to garmin connect using my apps, it's now a failure in the app, it's just that they require you to approve some lengthy text before you can keep uploading. Here is how you fix it:

- login manually to the garmin connect website (not the app - the website)

- click on the upload data icon (the cloud) on the top right:

garmin will prompt you to accept some stuff. My apps can't upload unless you do. So, read the stuff and if you agree, accept.

That's it. My apps will start working again like before.


​

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.

Update: Sportablet 9.5 and the Uploader for Garmin 8.5, published today, contain a fix for this issue.

Yesterday the guys at Garmin changed some details in the login procedure once again, but I didn't notice until today.

A fix has already been implemented, I just need to do a little more testing.

​Unless they change something else again (usually when they change something they make more changes shortly after) a new versions of my apps will be published today.

Please follow sportablet on facebook or twitter for updates.

Garmin Connect uploads have been erratic in the past few weeks, with many people complaining on twitter and facebook that they could not upload files through their computers. Of course, people uploading from my app suffered the same issues. There was little point trying to fix something that was clearly not on my end.

It seems that they made it stable now (or for now :-) but they made minor changes that required an update to my apps. Get the Uploader for Garmin 8.4 or Sportablet 9.4 to solve upload issues (at least while they're still working / until they change it again).

If you still have problems after upgrading my app:

1) check that your password complies with the new garmin requirements etc (see my previous post for details).

2) check that you can indeed upload files, either with your computer or by exporting the file from my app and uploading manually to garmin connect. If their website becomes erratic again, I can't fix it from here.

3) after that, get in touch from the contacts page as I may have to see a log of your transfer to garmin connect (don't send me a transfer log while reading from the watch as that doesn't really help :-)

Yesterday the guys at Garmin have changed their website and an update was required for my apps as well. I've just published Sportablet 9.3 and the Uploader for Garmin 8.3 on google play (may take a few hours before they become available for download), which from my tests works just fine. Those versions also include an update for Training Peaks.

Note: if after you update the app you're still having problems:

- open a browser and go to garmin connect (use a browser not the garmin app)

- if you are automatically signed in, sign out (click on the human on the left side toolbar and choose sign out), then sign in again.

- you may be asked to change your password to comply with the new garmin requirements. If you do, update correspondingly in my app.

- you may be asked to add your name (see picture below). My app can't do that for you so you have to comply before my app can upload.

 

Today the guys at Garmin have changed their website and uploading from my apps is now failing.

I have already analyzed the changes they made and implemented a fix, but I need more testing (and it's kind late in my timezone as I'm writing this). Unless they change something else tonight :-) I'll have a new version of the app pushed to google play tomorrow.

​You may also have to log into garmin connect and set a nickname if you haven't yet. Details will follow when I release the new version. 

Please follow sportablet on facebook or twitter for updates on this.

The recent change in Garmin Connect required some changes in my apps as well. Sportablet 9.2 and the Uploader for Garmin 8.2 should work just fine until the good guys at garmin deem necessary to break things again :-).

Remember: as part of this change, garmin has adopted more stringent policies on passwords. So first check if you need to update yours by logging in through a browser (not the Garmin Connect app - your garmin web account and your account on the garmin app, if you have it, do not necessarily share the same password). If an update is required, go trough with it and then update the password in my app as well. Note: if you auto-login into connect because of saved preferences, I suggest that you first log out of connect and then log in manually, otherwise you won't be asked for a new password.

As usual, this is the time when I invite you guys to follow the sportablet account on twitter or facebook (links here on the right). There is no marketing going on there. I use those channels only to inform you of important stuff (updates, issues, etc.)

[update: problem has been solved, see here]

The guys at garmin have made major changes again. In turn:

- they may require you to update your password. So log into their website from a browser, update the password if asked to, then update in my apps.

- they have changed the login procedure (at least) and my app won't work anyway as of this moment. I'm investigating the required changes, doesn't look like it will be a quick thing. I do not have an ETA, it's not an exact science.

If you have purchased the app in the past few days and you feel outraged, feel free to contact me for a refund (I'll need your order number). If you feel like you need to go and downrate the app on google play, go ahead; some have already done so, I'm no longer trying to explain why it's the wrong thing to do.

Please follow sportablet on twitter or facebook for updates. I need to focus on the fix. Thanks.

[update: I've just pushed the Uploader for Garmin 8.1  and Sportablet 9.1 to google play. It may take a few hours before they become available to you. They all work fine at this time, unless the guys at garmin change their mind again. If you still have problems, please check that you can at least log in and upload manually in garmin connect, because if their website doesn't work (they're doing heavy maintenance) there is no chance that my app can work. On the plus size, I managed to make the sign-in process slightly faster]

A few days ago I released a new version of the apps (8.0 /  9.0) fixing issues due to updates to the garmin connect websites.

Unfortunately those changes were just the beginning, and more have come, and the app is not working again. I know it's not pretty, but it's also not something I can control. I have to analyze the new protocol and come up with a fix. Again, I know you would like an ETA but reverse engineering is not an exact science.

If you have purchased the app in the past few days and you feel outraged, feel free to contact me for a refund (I'll need your order number). If you feel like you need to go and downrate the app on google play, go ahead: some people need to be on the left side of the IQ bell, so if that's your role I won't try to stop you.

Please follow sportablet on twitter or facebook for updates. I need to focus on the fix. Thanks.