Connect version 4.20 broke local http access?

Oh wow, Brandon.ConnectIQ, so let me clarify:

You have issue which affect tens of thousands of Garmin customers, break projects of tens of ciq developers, here on this thread you have solution which takes 10 minutes to implement (not including testing and deployment process), but even after month of discussions, you guys didn't even make decision how to handle it. (If you don't agree on impact, I am afraid this is just another consequence that you don't know your own platform that well). 

It may be marginal for GCM team, but the main problem is that from your and Coleman posts, its clear that even your team doesn't too much bother (so there is no one to force GCM team to re-prioritise). And I am sad to assume that you are ok with it. 

Lets be clear here, its not about one particular bug. You guys obviously doesn't have motivation to change current situation when your platform is loosing its usability for anything else than watchfaces and other simple apps. From CIQ Summit, I didn't have feeling that you are ok with scaring away all developers who have ideas to bring something other. And believe me, I hear complains even from those few big partners what you have. But lets not drag to general topics here - this discussion is already running here: https://forums.garmin.com/developer/connect-iq/f/discussion/7985/general-wishes-ideas-for-connect-iq-future/912867#912867  

BTW, Google didn't guide you to block local connectivity, they introduced ways to deal with this kind of the problem. So I would be careful to blame Android security policy here..

I am available to video-call if you want to discuss why I am so negatively dedicated here.

Oh wow, Brandon.ConnectIQ, so let me clarify:

You have issue which affect tens of thousands of Garmin customers, break projects of tens of ciq developers, here on this thread you have solution which takes 10 minutes to implement (not including testing and deployment process), but even after month of discussions, you guys didn't even make decision how to handle it. (If you don't agree on impact, I am afraid this is just another consequence that you don't know your own platform that well). 

It may be marginal for GCM team, but the main problem is that from your and Coleman posts, its clear that even your team doesn't too much bother (so there is no one to force GCM team to re-prioritise). And I am sad to assume that you are ok with it. 

Lets be clear here, its not about one particular bug. You guys obviously doesn't have motivation to change current situation when your platform is loosing its usability for anything else than watchfaces and other simple apps. From CIQ Summit, I didn't have feeling that you are ok with scaring away all developers who have ideas to bring something other. And believe me, I hear complains even from those few big partners what you have. But lets not drag to general topics here - this discussion is already running here: https://forums.garmin.com/developer/connect-iq/f/discussion/7985/general-wishes-ideas-for-connect-iq-future/912867#912867  

BTW, Google didn't guide you to block local connectivity, they introduced ways to deal with this kind of the problem. So I would be careful to blame Android security policy here..

I am available to video-call if you want to discuss why I am so negatively dedicated here.

Jim, that's actually part of the problem, the GCM team appears unresponsive to us and to the connect iq team. If that's really going to be the case then connect iq should just remove all functionality that uses gcm.

I hope you are using "you" in the Garmin sense, and not the Brandon.ConnectIQ sense, as he's on your side.  He's not the one to make the calls about what and when the GCM does something.