Error -300 on Fenix 3 and Fenix 3HR (7/31 workaround identified)

In the past 2 weeks, I have been getting an unusually large number of Fenix3/Fenix3HR users (4-5) contacting me with problems using my Weather Radar Widget. All of them are reporting getting an error -300 when doing the image download. There is not really anything have been able to do in the code, but I find it odd the the primary users I am getting problems from, 4 of the last 6, are F3/F3HR users and all of them are the same error, network time out.

Has anyone seen anything similar lately? Could it be an issue in an update to Garmin Connect Mobile? I remember early on the F5+ devices had problems downloading images due to GCM.

Not quote sure what to tell my users. In at least one case, it previously worked now they always get the -300 error. Any suggestions are welcome.

Workaround: I found decreasing the image height by 1 pixel works. So I now get a 216x218 image for devices with a 218x218 screen.

sabeard over 5 years ago in reply to jim_m_58

Jim, if it is a server end thing, then it is something they are doing with the image request that is only affecting the F3 family of devices. Those are the only ones I am seeing the -300 error code reports from lately. I have tried it with no issued on my FR230, so I know it still works on other CIQ 1 devices. I have personally tested on a FR935, FR230, VA3M, F5+, and Edge 1000 across 4 different phones (all android) and cannot reproduce a -300 error.

HermoT, my gut feeling is the same but I don't remember if there was a GCM update around that same time or not. I know a new release came out in the past week, and I know it did not fix anything if it is a GCM issue.

It could be a FW issue on the F3 devices, but I would not have expected that family of devices to have experienced a new FW in several months. So I would have expected that to be pretty stable. Which leaves to with one last thing that the 3.0.11 SDK did something in the last compile. Again, I would have expected that to be pretty stable also since the VM has not changed, but they do seem to correspond with an app update to add the latest devices supported with the new SDK.

akamming over 5 years ago

hi,

you are not alone, i just opened (did not realise this thread as already there) a topic with the same error (reported on FR630 and Vivoactive 3 Music)

https://forums.garmin.com/developer/connect-iq/f/discussion/166139/error--300

if you have a solution i'll be happy to hear it. I understand for most of the users it's working, but one my users is complaining, and all of a sudden i can reproduce on my own forerunner 630

sabeard over 5 years ago in reply to akamming

I don't have a solution. Everything works in the simulator, but not on actual F3 family of devices according to the reports I am getting. It also appears to be on both IOS and Android. I have not been able to find any other correlation yet. I don't know exactly when it started, but I do know that it has been a problem with GCM 4.19.

Travis.ConnectIQ over 5 years ago in reply to akamming

akamming- I cannot reproduce an issue making image requests on either the fr630 or the vivoactive3. I've posted working sample code in the thread you linked to above.

sabeard- I don't have a fenix3 family device available to test with, so this will have to wait until Monday. I have some ideas about what could be going wrong, but I'll need to be able to reproduce the problem first.

sabeard over 5 years ago in reply to Travis.ConnectIQ

Travis.ConnectIQ were you ever able to test this out. I got another report today from a user with a F3HR getting a -300. I have requested more details on the phone and GCM version they are using.

Travis.ConnectIQ over 5 years ago in reply to sabeard

Unfortunately, no. I work remotely, and don't have access to a fenix3 device to test with. I'll ping Coleman.Apps to see if he can test it out.

sabeard over 5 years ago in reply to Travis.ConnectIQ

Travis, thanks for the update. The latest user reporting the problem is using a F3HR with an iPhone XR running iOS 12.3.1 and GCM ver 4.20.0.14. let me know if I can provide more info.

This user had my app working but let the key expire and did not use the widget for a while. Recently he renewed his keys and started getting -300 errors everytime.

sabeard over 5 years ago

I think I stumbled onto the solution for this an a -402 error that started showing up on F3 family of devices. Starting with the SDK 3.0.12, I was able to reproduce the -402 error.

After some playing around I found out that if I reduce the height of the image by 1 pixel the issues go away. Basically what I do is get the screen height and width so I can download a full screen image and control the size by limiting the color palette. In this case it appears that something in the way GCM interacts with an 218x218 image on the F3 devices changed in the last couple releases. Other devices with the same resolution, F5s for example, work fine.

My simple fix was to just decrease the image for round watches with 218x218 screens to 216x218.

trudelta over 3 years ago

Experiencing the same problem on the V4S S/W version 6.3, GCM 4.47.1.2 on iOS. The workaround mentioned above works! really strange.