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.

HermoT over 5 years ago

One issue that was experienced about a year ago required users to restart their devices.

The bug was related to a counter reaching the max of an unsigned 16 bit integer (65535)

After a restart, the web requests would continue working but then typically stop again in a week to 2 weeks period.

I'm not saying this is the same issue, but you could start by asking your users to restart their devices and see if it makes any difference.

I'm sure ekutter-dnu and jim_m_58 might be able to contribute here.

jim_m_58 over 5 years ago in reply to HermoT

Hermo, in that case, the error was always -2. I'd still suggest restart the device though.

Scott - is there anything common as far as GCM? Are they all Android users or all iOS users?

HermoT over 5 years ago in reply to jim_m_58

Thanks Jim, you have a much better memory than I do!

jim_m_58 over 5 years ago in reply to HermoT

It's actually called "Jim's Big Box of CIQ Trivia"! :)

sabeard over 5 years ago in reply to jim_m_58

Jim, I have not been able to find that correlation yet. I just threw out the GCM as a theory knowing it is a key link in the web request path and based on the one past issue, when the F5+ came out, it was possible that a bug in GCM could effect a single device differently than others. I do remember seeing a couple GCM updates in the past few weeks.

I will suggest that everyone who is getting the issue restart their watch and maybe phone to see if that clears it up. I will also request their phone type to see if there is an iOS vs Android issue.

Thanks for the ideas.

sabeard over 5 years ago in reply to jim_m_58

After contacting all the users seeing the -300 error, I got responses from three of them. Two are running Android, and one is IOS, so it is not limited to the GCM mobile type. Although that is not a large sample size.

HermoT over 5 years ago in reply to sabeard

And no changes after restarting devices?

sabeard over 5 years ago in reply to HermoT

None!

HermoT over 5 years ago in reply to sabeard

That’s too bad. Wonder what it could be. My gut feeling is GCM.

jim_m_58 over 5 years ago in reply to HermoT

Both Android and iOS doesn't sit well in my gut.

Scott - is there any chance that this might be a server end thing?