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.

Brandon, thank you for the update. Here's hoping for a positive outcome for all concerned.

This issue has not been forgotten! Please understand that this arose because of changes to Android security policy, and not because of arbitrary changes to Garmin Connect Mobile (or Connect IQ, for that matter). Our mistake, admittedly, was not being aware of how this was being used by Connect IQ developers and not accounting for your use cases when the changes were made in Garmin Connect Mobile to comply with Google's guidance.

My team has been advocating for you, and as a result, there was quite a bit of discussion about how we can address this during July. We don't yet have a decision, so there isn't much to share right now. We'll continue to stay on top of this so we can provide an answer as soon as possible. 

off course, but in organisation like Garmin, its CIQ team responsibility to explain them impact, negotiate work on solution and keep track of the process to be able to handle proper communication with developer community. 

I guess it's just not bothering the GCM tribe at all when there is a commotion in the cIQ bug tracker. They won't even mind when logs and play store data are showing a bunch of people clinging to 4.19, because thanks to fitness watches going mainstream they have a lot of very casual users who dominate the stats.