There have been many report of issues with the latest version of the iOS / iPhone Garmin Connect App (v1.2.x).
(Note before the version 1.2 upgrade all worked well!!)
Since the version 1.2 upgrade people are experiencing:
(1) App Crashes Downloading Activities. When App is restarted any already downloaded activities are wiped and it starts downloading them all again - this is hitting people's download allowance and must be stressing Garmin's servers!! This is very frustrating because it means a long wait before you can download any new activities from the Garmin 510.
(2) Live track stops working most of the time.
Anyway as I am an iOS developer I have access to the crash logs so decided to dig a bit further to see what is happening for the App crashes. When the App crashes the following crash logs are produced:
[FONT=Courier New]
Incident Identifier: 8B1404E6-05B7-48A7-877D-737D28221EA9
CrashReporter Key: 6f9d4d55d58eec3b21868f58997f09edc4c5e1f0
Hardware Model: iPhone5,2
OS Version: iPhone OS 7.0.3 (11B511)
Kernel Version: Darwin Kernel Version 14.0.0: Fri Sep 27 23:00:47 PDT 2013; root:xnu-2423.3.12~1/RELEASE_ARM_S5L8950X
Date: 2013-11-04 19:35:48 +0000
Processes
Name <UUID> rpages recent_max fds [reason] (state)
ConnectMobile <5d9497e623af37af8ca6322072f2bb7c> 165418 165418 200 [per-process-limit] (frontmost) (resume)
[/FONT]
Basically what that is telling me is the ConnectMobile app (assume that is the Garmin Connect App - nothing else was running at time of crash) - is using far too much memory and iOS says enough and kills it. 165418 x 4k blocks - THAT IS OVER 600mb in use by App!! So basically there is a massive memory leak in the app that needs fixing - soon please!
Happy to assist the Garmin developers or test any beta versions ... because I would like my Garmin 510 to work like it used to asap.