This is exactly why I stopped being a CIQ developer. Too frustrated to be either a developer or end user.
Any news? I'm actually tired of using a workaround with NanoHTTPD server and watch talking to that server.
I implemented this interval technique but it does not matter the problem it's just that the problem will appear later.
I can confirm that too, I have users with different types of watches that are experiencing the issue. I'd love to use the NanoHTTPD route where the watch polls instead but it looks like the latest version of GCM introduces a problem with non TLS requests on localhost (https://forums.garmin.com/developer/connect-iq/i/bug-reports/connect-version-4-20-broke-local-http-access) this makes it very hard to develop now.
Coleman.Apps Could you please post any update on this?
Coleman.Apps Could you please post any update on this?
I have released an application with this concern and I only receive negative comments from users who do not understand that it is not my fault. For some phones it works perfectly suddenly they are happy, so I would tell you to even take it out because it is a shame to have worked for nothing otherwise.
I thought so too, but I was planning to charge money for this app, and I don't feel comfortable doing so, knowing that every other day the main and only feature won't work
I've updated the samples for newest SDKs of both Android and ConnectIQ, added some extra logging and also included prebuilt APK for easier testing. Issue is still present.
Please take a look Coleman.Apps or please forward to someone else. Thank you
Was there any work on this in the latest Garmin Connect update? Coleman.Apps