Connect version 4.20 broke local http access?

Thanks a lot for the provided info Brandon, although this "not knowing" is far from happy news. 

With this approach seen also on past resolutions of other issues related to the CIQ platform, Garmin sends clear message how insignificant is Connect IQ for the company and how we developers will be treated even for the future. Obviously CIQ didn't grow fast enough for your managers - we can only debate what was the primary cause. I decided to invest lots of my energy (and money) recently to try to bring more of stronger outdoors companies to your platform, but not only number of issues along the development of the app for the first one is surprising, but this current issue - genially "planned" to cover most of of summer prime-time - is probably not something from what I will recover to continue with other negotiated companies. One would say this is not exactly on par with your strategy... 

So I keep asking what are the actual goals for CIQ platform and how Garmin organisation structure look like. Because from outside it seems that manager of one team is prohibited to talk to manager of second team and do some effective decisions to move things further. I was part of such company once, and it was sad experience. 

This is just simple summarization how I feel as developer of your platform when I am not trying to implement simple watchface or another basic-formula datafield. And I am not the only one.

BTW, if anybody manage to have local connectivity via https from Android, let me please know - I already gave up. 

Thanks a lot for the provided info Brandon, although this "not knowing" is far from happy news. 

With this approach seen also on past resolutions of other issues related to the CIQ platform, Garmin sends clear message how insignificant is Connect IQ for the company and how we developers will be treated even for the future. Obviously CIQ didn't grow fast enough for your managers - we can only debate what was the primary cause. I decided to invest lots of my energy (and money) recently to try to bring more of stronger outdoors companies to your platform, but not only number of issues along the development of the app for the first one is surprising, but this current issue - genially "planned" to cover most of of summer prime-time - is probably not something from what I will recover to continue with other negotiated companies. One would say this is not exactly on par with your strategy... 

So I keep asking what are the actual goals for CIQ platform and how Garmin organisation structure look like. Because from outside it seems that manager of one team is prohibited to talk to manager of second team and do some effective decisions to move things further. I was part of such company once, and it was sad experience. 

This is just simple summarization how I feel as developer of your platform when I am not trying to implement simple watchface or another basic-formula datafield. And I am not the only one.

BTW, if anybody manage to have local connectivity via https from Android, let me please know - I already gave up. 

I agree with Jan - with this and other Connect regressions, as well as other CIQ networking limitations that prevent me from providing real functionality, its clear Garmin isn't serious about CIQ and I have adjusted the effort I put it to apps accordingly.