As of last night, February 23rd, the Garmin service changed and now ConnectStats receives Service Logic Error as Garmin is rejecting the current approach ConnectStats uses to access the Garmin web page information.
I am pushing a new version that fixes the issue, hopefully will be approved soon by apple,
As explained here, you can still access your activities by making sure you use the ConnectStats service, which is still working. For that follow instruction in the link and make sure you select for Garmin Source “All” or “ConnectStats”. This should let you access new activities properly.
Please note that if you enable the connectstats service for the first time or if you are a new user of the app, you will not get any activities prior to you registering for the service, as Garmin only sends new activities after you registered. I’ll see how to improve that or write about how to work around it later.
I’ll update further when I have time to properly investigate and see if there can be a workaround.
Sorry for any inconvenience, please check here again later for updates
Users reported an occasional Access Denied error with the Strava service and last week ConnectStats release. Thanks to the bug report, it was fairly easy to get to the specific workflow in the strava service that was confusing ConnectStats. The fix was the easy part. Then I went on to the dreaded “submit and get apple approval” part of the release process.
The review process is a bit of a black box random process. You submit the same application over and over and sometimes it’s approved in a day, sometime faster, sometime slower, and sometime you get “Rejected”…
Living in London, the year end period ended up in new strict lockdown with very few options but to spend a lot of time at home, and skip the traditional visit to my family in France and Switzerland. Luckily me and my family stayed safe so far.
I took the opportunity of being at home to make quite a few changes to ConnectStats both internally and externally…
If you maintain an app like ConnectStats that has a lot of local files on the device and does not rely on the cloud constantly for input, each time Xcode upgrade all the iOS Simulator starts empty again and loose all the files from the previous version.
The iOS simulator keep it’s file in some complicated folder structure and the folder change each time you start it, so it can be quite tricky to locate the files. And so quite painful to locate all the folder for the previous and new version and move all the files over.
Garmin sends ConnectStats all the data as Fit Files, so I had built a library to parse it for the app. I used the code from the official Fit SDK. Originally I used the c++ implementation provided in the SDK as it was providing a way to get all the data pretty generically. The SDK while quite generic was actually quite slow in parsing.
About 2 years ago, as I wanted to get ConnectStats to get the extra information from the fit file and parse them systematically for each activity, the speed started to become an issue. So I wrote a new library in swift based on the c implementation of the SDK.
That ended up much faster than the previous version, and ConnectStats has been using it for a while, as well as FitFileExplorer which is a tool I wrote to see the raw fit files.
While I had provided that library on GitHub and it was open source, it wasn’t really easy to integrated into another app. Following a request last week, I investigated how to make it a Swift Package which I wasn’t really aware of. Always a good challenge to learn something new!
One of the requirement for me in finding a new house was to make sure it had ethernet cabling everywhere so I could ensure I have a stable network and enough access point to get good wifi connectivity in every room.
When I moved into a new place in August 2016, it met the requirement, but to my and my family dismay, the network and wifi stability was dreadful. It consistently would stall time and time over again. Streaming movies or music want halt for minutes at a time, and reading news on the web would also randomly hang.
I embarked on a long journey to try to resolve the issue, which would lead me to learn way more about networking that I ever imagined possible…
ConnectStats history with the weather had a few chapter. First, I started to get the data from the Garmin Website so I could display the condition, the temperature and mostly the wind direction and speed in the map, which is always a good visual clue of how the wind helped or hurt in an activity.
When Garmin stopped publishing its weather data in the API, ConnectStats ended up without the weather for a while. Until Garmin opened its new API which required me to implement my own server, and indirectly made it easier to query the weather to display in an activity.
I live and do most of my running in London, where it can be quite hard to find any type of hills and the elevation gain field from my activities is never the most relevant.
This summer I managed to escape London twice. The first week when the UK lifted travel restrictions and quarantine early July, I went to the mountains of the Valais in Switzerland and the last week before the quarantine was restored, I went to south france, 30 kilometres in land from Nice, where the Alps ease into the sea. So I got my share of opportunity for testing how to slice and dice elevation gain in ConnectStats.
To keep motivated, I also took a few Strava Challenges, including the august climbing challenge of running at least 2,000m of elevation. It became clear that ConnectStats required a few enhancement to properly track my progress on elevation gain…
At the moment ConnectStats is not working properly when using the Garmin Data from the ConnectStats Servers. I’ll explain the issue, but there is a temporary work around
UPDATE: I have a new version pending approval from Apple that will work without the work around. With version 6.2.1, if you have “all” as a source, the app will automatically go to the web site if the ConnectStats Server didn’t receive data from the Garmin Health API.
Update as of August 6th the issue with the garmin api is resolved. So no need for the work around and using all as data source should be fine.
I you are having ConnectStats not display an activity or statistics or hanging you need to
Select the last good activity you have in your list (does not have to be the last one but a known good one)
Go to Config, Profile and select “Delete Some Activities”. This will delete all the activities from the app up to the one you have selected. It will not delete anything on any server, only in the app local files.
Go to Config, Services, Garmin and select for Source “Garmin WebSite”
Close the app fully (may not be necessary, but to ensure there are nothing in the memory cache)
Restart the app and try to download activities again.
When thing works again, you should be able to revert source to “all”, but monitor here or on twitter for message that it’s fixed
What is the issue
Since early today, the Garmin API is sending error instead of the activities files to the ConnectStats server. As a result the app is trying to go the Garmin website directly to get the fit file. Currently Garmin Connect is not letting you download fit files (if you go to garmin connect and select “export original” you will get an error), this second error is causing ConnectStats to hang on its processing queue (my bug).
If you select Garmin WebSite as a source it will get the data of your activity without trying to get the fit file and this seems to work at the moment.
I’ll update this as the situation evolve and post on twitter as well.