Garmin Connect app crashes on makeWebRequest

Hi

Since the latest update of the Garmin Connect iOS app, makeWebRequest (GET) fails with error -2 and Garmin Connect crashes (if running in foreground). It still works on the simulator and it has been working on my Forerunner 630 prior to this update. Has anyone else experienced this?

It doesn't crash right away, but after 4-5 makeWebRequest calls it does.

Forerunner 630 version 3.30 6cdb18e
Garmin Connect app version is: 3.12.0.8

An other thing I've noticed is that the "Updating" spinner keps showing up on my FR once every minute, which is very annoying.

Regards
Jonas

Brandon.ConnectIQ over 8 years ago

Thanks for the report - I've filed a ticket to have this investigated.

jokarls over 8 years ago

Great!

Btw here's a (truncated) crash report from my iPhone

{

   "app_name":"ConnectMobile",

   "timestamp":"2016-11-29 20:23:35.98 +0100",

   "app_version":"3.12",

   "slice_uuid":"c3542fb8-2506-3154-8a5f-c2e9783024c0",

   "adam_id":583446403,

   "build_version":"8",

   "bundleID":"com.garmin.connect.mobile",

   "share_with_app_devs":false,

   "is_first_party":false,

   "bug_type":"109",

   "os_version":"iPhone OS 10.0.2 (14A456)",

   "incident_id":"EC2CF03D-4530-4EC2-ABD9-140CB6FE44C5",

   "name":"ConnectMobile"

}



Incident Identifier: EC2CF03D-4530-4EC2-ABD9-140CB6FE44C5

CrashReporter Key:   db9a1a6709850c81d96fa1112875f917a0ecd3a1

Hardware Model:      iPhone7,2

Process:             ConnectMobile [29746]

Path:                /private/var/containers/Bundle/Application/BD21587F-6C34-4299-9DD1-CE9F2D731CA2/ConnectMobile.app/ConnectMobile

Identifier:          com.garmin.connect.mobile

Version:             8 (3.12)

Code Type:           ARM-64 (Native)

Role:                Non UI

Parent Process:      launchd [1]

Coalition:           com.garmin.connect.mobile [10316]





Date/Time:           2016-11-29 20:23:35.4121 +0100

Launch Time:         2016-11-29 20:22:54.2677 +0100

OS Version:          iPhone OS 10.0.2 (14A456)

Report Version:      104



Exception Type:  EXC_CRASH (SIGABRT)

Exception Codes: 0x0000000000000000, 0x0000000000000000

Exception Note:  EXC_CORPSE_NOTIFY

Triggered by Thread:  0



Application Specific Information:

abort() called



Filtered syslog:

None found



Last Exception Backtrace:

(0x1943681c0 0x192da055c 0x19436f278 0x19436c278 0x19426659c 0x194e6d610 0x100254db4 0x100252b80 0x100250458 0x101b0ca4c 0x101b0f748 0x101729998 0x101697874 0x1017200f4 0x1931f1200 0x1931f11c0 0x1931f5d6c 0x194315f2c 0x194313b18 0x194242048 0x195cc5198 0x19a21c628 0x19a217360 0x10006d02c 0x1932245b8)



Thread 0 name:  Dispatch queue: com.apple.main-thread

Thread 0 Crashed:

0   libsystem_kernel.dylib        	0x0000000193336014 0x193317000 + 126996

1   libsystem_pthread.dylib       	0x00000001933fd460 0x1933f8000 + 21600

2   libsystem_c.dylib             	0x00000001932aa490 0x193247000 + 406672

3   libsystem_c.dylib             	0x00000001932aa400 0x193247000 + 406528

4   libc++abi.dylib               	0x0000000192d752d4 0x192d74000 + 4820

5   libc++abi.dylib               	0x0000000192d92cc0 0x192d74000 + 126144

6   libobjc.A.dylib               	0x0000000192da0844 0x192d98000 + 34884

7   ConnectMobile                 	0x0000000100c169c4 0x100054000 + 12331460

8   libc++abi.dylib               	0x0000000192d8f66c 0x192d74000 + 112236

9   libc++abi.dylib               	0x0000000192d8ef84 0x192d74000 + 110468

10  libobjc.A.dylib               	0x0000000192da0690 0x192d98000 + 34448

11  CoreFoundation                	0x000000019436f278 0x194239000 + 1270392

12  CoreFoundation                	0x000000019436c278 0x194239000 + 1258104

13  CoreFoundation                	0x000000019426659c 0x194239000 + 185756

14  Foundation                    	0x0000000194e6d610 0x194d44000 + 1218064

15  ConnectMobile                 	0x0000000100254db4 0x100054000 + 2100660

16  ConnectMobile                 	0x0000000100252b80 0x100054000 + 2091904

17  ConnectMobile                 	0x0000000100250458 0x100054000 + 2081880

18  GarminDeviceSync              	0x0000000101b0ca4c 0x101af8000 + 84556

19  GarminDeviceSync              	0x0000000101b0f748 0x101af8000 + 96072

20  GarminDeviceIO                	0x0000000101729998 0x101660000 + 825752

21  GarminDeviceIO                	0x0000000101697874 0x101660000 + 227444

22  GarminDeviceIO                	0x00000001017200f4 0x101660000 + 786676

23  libdispatch.dylib             	0x00000001931f1200 0x1931f0000 + 4608

24  libdispatch.dylib             	0x00000001931f11c0 0x1931f0000 + 4544

25  libdispatch.dylib             	0x00000001931f5d6c 0x1931f0000 + 23916

26  CoreFoundation                	0x0000000194315f2c 0x194239000 + 905004

27  CoreFoundation                	0x0000000194313b18 0x194239000 + 895768

28  CoreFoundation                	0x0000000194242048 0x194239000 + 36936

29  GraphicsServices              	0x0000000195cc5198 0x195cb9000 + 49560

30  UIKit                         	0x000000019a21c628 0x19a1a1000 + 505384

31  UIKit                         	0x000000019a217360 0x19a1a1000 + 484192

32  ConnectMobile                 	0x000000010006d02c 0x100054000 + 102444

33  libdyld.dylib                 	0x00000001932245b8 0x193220000 + 17848

Regards
Jonas

Coleman.Apps over 8 years ago

Jonas,

We've been working on trying to reproduce your issue with our samples, but have had no luck so far. Could you provide us with some sample code or a test project that reproduces the issue? You can send it to [email][email protected][/email]

Thanks,
-Coleman

jokarls over 8 years ago

Ok, I've sent you an email with the code that fails on my watch/phone.

Regards
Jonas

JohanGranlund over 8 years ago

Any updates on this issue?

Did you do any progress on this matter?

regards,

Johan

Coleman.Apps over 8 years ago

We have not been able to reproduce this on anay devices that we have in office. I know that there has been a similar bug reported that is currently being looked into by the Connect Mobile team. Let's see what happens with the next update to GCM in iOS because I think the fix will be there. If you are still experiencing the issue. I'd like to start a new ticket using the Bug Reports Forum.

Thanks,
Coleman