Yesterday the guys at Garmin made some changes and broke my apps, so when you try to upload you get a communication error.

I'm aware of the issue. I need a few days before I can set aside the necessary time to analyze the changes and see what has to be done to get the apps working again.

Meanwhile, if you feel the urge to go to google play and write a 1* review, go ahead. I've long lost any hope on that side. You might get a snarky answer, but that's it.

[UPDATE - May 20] This is looking worse than usual. It's not a "normal" change to the website structure or login workflow. This change has been made exactly to prevent third parties and scripts to login / upload to garmin connect (I can see that from the error message I get). It will take way more time than usual to find a reasonable solution to this issue.
​>> No, I don't have an estimate.

[UPDATE - May 22] I made some decent progress, but it needs more testing. 

[UPDATE - May 23] Sorry, the door I found has already been closed. Back to square one. 

[UPDATE - June 6] Still no go news. For those who may want a few technical details: Garmin has adopted Cloudflare to prevent non-interactive access to their website. At this time it's rather clear that the entire network stack I'm using has been fingerprinted down to the TLS level, so there is no way to circumvent that through some clever coding up the stack. I need to switch to an entirely different network stack. The first step of course it to find one that has not been fingerprinted (yet). Then I have to rebuild all the logic using the new stack, but that shouldn't take too long. Of course, it may not last much anyway, but I'll give it a try. Still, it's going to take me some time.
​
Meanwhile, remember that you can still read data from your Garmin using my app, then email yourself the file (there is a button for that at the bottom of the list, just scroll down) or export as a FIT/TCX (don't export as GPX as that loses some information) and then upload the file on Garmin Connect manually (from the browser on your phone). I know it's a nuisance but might still be a decent option when traveling without a computer.

​

A few days ago the guys at Garmin made some changes to the login procedure, which broke my apps.

I have immediately released a fixed version of the app (previous post) but without public announcement, to make sure further instabilities didn't ensue in the next few days. Everything seems stable so here you can find the updated APK files:

sportablet apk  << click to download from google drive

uploader for garmin apk  << click to download from google drive

Once downloaded, you'll have to install the app from the file manager (if you've never installed an app given the APK, there are many tutorials, like this: https://www.wikihow.tech/Install-APK-Files-on-Android). The APKs are signed with my developer key just like the ones from google play, so they will install over the old version just fine.

As I have anticipated in previous posts, I won't be able to push new versions to google play for the time being, so publishing the APK here will be the standard procedure from now on.
(The rather simple reason is that Google now requires all the updates to target android 9, and for an hardware-dependent app like mine that's a lot of work, especially in testing, with no real value for the end user. The app has been earning pretty much nothing for the last few years, so it's hard to justify all that work).

Today (or perhaps yesterday) the guys at Garmin made some changes to the login procedure, which broke my apps.

I already have a fix ready, but since Garmin often makes changes in short sequences, often during the weekend, I'm planning on waiting 1-2 days before releasing a new version, to see if things are stable or not.

Unfortunately, as I have anticipated in my previous post, I won't be able to push the new version to google play. Google now requires all the updates to target android 9, and for an hardware-dependent app like mine, that's a lot of work, especially in testing, with no real value for the end user. The app has been earning pretty much nothing for the last few years, so it's hard to justify all that work.

herefore, I'll publish the APK file here and you'll have to install the app from the file manager (if you've never installed an app given the APK, there are many tutorials, like this: https://www.wikihow.tech/Install-APK-Files-on-Android).

If you really need to upload right now : ), or just feel like testing the new version, get in touch and I'll send you the APK. It is, of course, signed with my developer key just like the one from google play, so it will install over the old version just fine. Remember to tell me if you need the uploader or the sportablet app.

Update: seems like you guys can't wait so here are a couple of links:

sportablet apk

uploader for garmin apk


​

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 :-)