Yet another Garmin Connect update...

2/20/2014

Update: I've just pushed Sportablet 6.5 and the Uploader for Garmin 5.6 to google play. Should be working fine with the new login procedure. If you have any trouble, get in touch.
--

Yesterday the guys at Garmin have updated the Garmin Connect website, which looks nicer : ) but is also using a different login procedure. As I've already said a few days ago, Garmin does not have an official API to upload data to garmin connect. Things can break. This time you get a different error message ("Can't login").

To make it a little more challenging, it seems they're rolling out the update selectively. I'll try to find a way to make the login procedure compatible with the old version (for those of you who are still mapped on the old website) and the new.

Please, if you want updates on this, follow the sportablet account un facebook or twitter. I can either spend my time trying to fix the app or answering all the emails :-).

23 Comments

Andrew Rich link

2/20/2014 02:45:50

I see the new login screen when I go to Garmin Connect, so I'll look forward to an update to your wonderful app.

Arniegeddon

2/20/2014 02:45:56

Thanks for the update :)

ben

2/20/2014 04:18:21

Just bought this app (garmin uploaded) 3 days. Was working great. Now this. Bugger! Thanks for fixing it asap, cannot wait for the update.

gasteropod

2/20/2014 05:11:43

I'd be even more worried by:

Get ready for the biggest makeover Garmin Connect has ever seen. In the next several weeks, we’ll begin granting access to the new site.

My guess is that this could well break things in a bigger way.

carlo pescio

2/20/2014 06:29:32

sure, it's quite likely that we'll face some instability in the foreseeable future. With a little patience and determination, everything will be just fine in the end : )

Andy

2/20/2014 13:13:02

Thank you for the quick updates following the last few Garmin site issues. Uploader is a fantastic app!

Walid

2/20/2014 18:57:01

Forerunner 610 uploads just fine in USA! Thanks for the quick fix! Very appreciative.

ben

2/21/2014 01:18:45

All fixed, great work! Many thanks.

alunpg

2/21/2014 01:58:12

Well done!! Thanks for such a quick fix! :D

Rasmus

2/22/2014 03:28:53

Hi Carlo,

We are a few in the same boat as you: Working with unofficial garmin connect api. The change to sso.garmin.com has caused quite a few ppl problems, but judging from you post, you appear to have solved it.

If you have the time, shedding a bit of light on how you solved it would be greatly appreciated. We have an active thread at following url:

https://forums.garmin.com/showthread.php?72150-connect-garmin-com-signin-question

Best regards,
Rasmus

Meex link

2/22/2014 12:56:15

Hi Carlo,

may you can give me/us a little hint how you solved the signin issue with the new sso.garmin.com

regards
Meex

arnout

2/23/2014 22:46:01

Seems to have hit all apps.
http://www.dcrainmaker.com/2014/02/reviewfebruary-23rd-2014.html

Rainmaker replied
February 23, 2014 at 8:47 pm #16
Yeah, Wahoo and pretty much everyone else broke on Thursday. Garmin changed a few things, which in turn broke most programmers. I’ve been playing a fair bit of shuttle diplomacy over the past few days, and I think the majority of app-devs that broke are on the bus to getting access to the new API (hopefully tomorrow). They had to agree to what looked like a fairly standard API terms agreement first.

Once they get access to the API, then they’ll need to update their own apps, then publish to the various app stores, which, could take some time.

Garmin states it was unintentional, though, I’m honestly not sold on that one. Testing just one single app would have told them it broke everyone (which it did). Sigh.

future?

3/12/2014 05:12:50

I've just read, that Garmin introduces $5000 paid license for 3rd party companies. How does it influence on SportTablet and Uploader and GC?

carlo pescio

3/12/2014 10:46:37

where did you read that? I've only found a reference here:
http://ro-z.net/blog/2014/03/05/garmin-connect-new-policy-impact-on-connectstats-and-3rd-party-apps/
however, it mentions a private communication with garmin, and I had none.

gasteropod

3/12/2014 10:51:28

http://www.dcrainmaker.com/2014/03/garmin-vivofit-review.html which says:

As part of the transition to GC2, that API access was deprecated and companies instead must apply for access to the data. The entry fee for access to the data upon approval is $5,000. While there are a number of major companies that are poised to start using the new API in the coming weeks/months, none of them are yet public about it. Previously it had leaked out via REI’s website that MyFitnessPal would be a partner – but that hasn’t materialized yet (and has since been redacted from REI’s site).

Ultimately, with the $5,000 admission fee, you’re more likely to see larger companies than smaller companies or hobbyists access the data – which are effectively shut out from Garmin’s platform.

Rasmus

3/12/2014 11:07:34

@carlo, I received a response from Garmin Connect team stating both a fee and vetting process. The exact words:

Garmin has instituted a new policy regarding the accessibility of our developer programs. The previous strategy of freely available APIs quickly became unsustainable due to increasingly high demand. In response, we have established a new pathway for our Connect API. Firstly, there is a vetting process. We are strategically limiting the scope of this program to specific developers that will enhance the user experience. Secondly, those who are approved for inclusion will be charged one-time $5,000 administrative fee to cover the extensive engineering and server support required for the Connect program.

carlo pescio

3/12/2014 11:05:16

well, it depends on how they intend to proceed (technically or by other measures). I'm not really worried about technical issues. Endomondo and Runtastic don't offer an API at all, but I managed to send data anyway. It may take time to learn and adapt, but that's all.
In the end, these apps are a pet project, there is no serious money here. Worst case, I'll have to drop support for connect, and keep supporting the others.

gasteropod

3/12/2014 11:07:48

Yes, there is normally a way. I have often uploaded to sites with no API by simply simulating what a browser would do with a manual upload. e.g. SportTracks until you could upload via their API.

Alex

3/12/2014 15:02:37

I try to send a tcx file downloaded from gpsies.com to my edge205.
It fails: can't /mnt/sdcard/track.tcx
Exported tcx from sporttablet is working fine.

Support would be appreciated., this is my main usecase

carlo pescio

3/12/2014 15:07:28

instructions are here:
http://www.sportablet.com/send.html

from your error it seems like you didn't put the file in the right place with the right name.

If that's not the case, send me a log and maybe the file, it's hard to see what's going wrong from here!

Alex

3/13/2014 12:29:27

Thank you for your reply,
Filename is correct. I found out that Gpsies uses another tag structure for tcx format.
I send you the file and details.

carlo pescio

3/19/2014 03:07:33

that format is now supported in the Uploader for Garmin 5.7 and Sportablet 6.6 (www.sportablet.com/send.html). The CRS format should work as well, as long as you still call the file track.tcx.

Alex

5/1/2014 16:23:39

Thx, gpsies.com imports are working fine now.
Good work!

About me

I'm a decent runner, ex mountain biker, and a good swimmer. I created Sportablet to squeeze a little more fun out of my Forerunner.

In my everyday life, I design software-intensive systems at different scales, using a number of paradigms, languages and technologies.
You can read some of my thoughts at carlopescio.com

Yet another Garmin Connect update...

Leave a Reply.

About me

Archives

Categories