Odd makeWebRequest behavior with Widget vs App on F6 pro while connected to GCM 4.47.2

I just updated my widget to consolidate two makeWebRequests into a single network transaction. At the same time I released a app version of the widget which is based on the exact same code with the exception of a couple string entries to designate the widget from the app. The web query is designed to check the device registration status and return the current expiration date of the trial or registration. Yesterday I got a report that the widget was not recognizing the registration after saving the settings on a F6pro. I tested on my own F6pro and was able to reproduce the issue. I can see the issue in both my released widget and the beta test build, but my new full device app version is able to work properly. Based on the behavior the widget is acting like it is not getting the response from the webserver, even though in the webserver logs I can see the query get returned with a 200 OK message.

After doing some testing in the simulator, I have verified that the code is working as planned. I can see in the HTTP log in the simulator provide the query and the return response. I also enabled some println calls to display the returned value and display the variable which were updated from the response. I did a test build of my beta widget so I could enable logging on the real device. After installing the beta widget on the device and adding the text log file, my theory was confirmed. I can see in the log file the outgoing makeWebRequest URL where the request was sent. I can see the 200 OK in the webserver logs. I never see the callback method get called so the results can be parsed and updated on the device. What make it more confusing is the full device app version still works fine. So I know the code does work as intended.

I also tested the widget on a VA3m and both the app and the widget version worked just fine so I have to believe it is caused by something either with the device FW version, or with how GCM is interfacing between the watch and the internet. My guess is something with the latest version of GCM is causing the problem because I had no problems with the widget on the F6pro when I first installed the test build of the widget on Sept 19 using GCM android 4.47.1. Over the weekend I update GCM android to 4.47.2 and now thing are broke. I also confirmed with the user reporting a problem that they to are running GCM Android version 4.47.2. To make matters more confusing, the same widget on an F5pro, connected to the same watch works fine.

I don't understand how two different CIQ apps on the same device using the exact same functions can have completely different results when run. One never sees the call back and the other works fine.

Any recommendations on how to troubleshoot?

_psx_ over 4 years ago in reply to sabeard

I've read somewhere about problem when you run makeWebRequest in intialise or "too early place" move it to onShow onDraw to timer etc

jim_m_58 over 4 years ago in reply to sabeard

I have a few widgets that do makeWebRequest calls, and have not heard of any problems like this from any f6 pro users.

This is indeed strange!

sabeard over 4 years ago in reply to jim_m_58

And what makes it stranger for me is your widget works fine on my watch, but mine does not call the onReceive function. I am trying a test build with an older SDK which I knew previously worked, to see if could be related to how the SDK built the project.

sabeard over 4 years ago in reply to _psx_

I have tried the makeWebRequest call in multiple locations, it has not made any difference. If it was a problem with location, then I would expect all devices to have the same issue, not just the F6pro devices.

_psx_ over 4 years ago in reply to sabeard

Another problem can be with Connect (Samsung e.g put app in deep background) but in my case I receive onReceive but with errors -300, -5

I have f6pro so I can test it for you.

sabeard over 4 years ago in reply to _psx_

I too have an F6pro. I can see the request make it to the webservice and I can see the outbound response from the server. I just never see the response make it back to the watch. If you want to test, you can use the following link to install the widget. When the image loads, you will see trial and a date on the screen. If the date is within 2 days then you are seeing the same bug. If the date is 3 weeks later, then you got the response from the server. I am pretty sure you will see a 2 day trial.

https://apps.garmin.com/en-US/apps/9c692f27-57d6-4488-91ae-5dd846a4ad26

At this point it would be helpful to hear from a F6pro user with an iPhone to see if it too has the same problem. I don't think it will.

jim_m_58 over 4 years ago in reply to sabeard

The current store build of mine are with 4.0.7, and I'm running side loads built with 4.1.0-beta1 too. My f6 isn't a pro, so can't test what you're seeing

sabeard over 4 years ago

After about 5-6 months scratching my head on what to do with this bug that only affected seemed to affect F6pro devices when paired with an android phone, it looks like a solution is in the works. I just installed the F6pro beta 20.82 which adds the system 5 to the device and my widget now runs properly again. I have made no code changes or new builds since the problem began, so I can only say it must have been a FW issue.

jim_m_58 over 4 years ago in reply to sabeard

I found there have been FW/CIQ fixes to the f6 devices over the last few months, and I bet System 5 added a few more! This was sure a strange one!