I have a user that has a fenix 5 wifi and he says on two of my apps he is getting a "iq!" Error. I can not replicate this in the simulator has anyone else seen this? These apps work fine on my f3hr.
I think the problem is corrected. Last night I noticed that even though I downloaded the latest sdk, I had not activated it in eclipse. I tested it on one of new faces and one of my users said it now works on their F5wifi. Maybe others are having similar issue then?
My gut tells me if you had a version of the SDK with F5 support before, getting the newest (2.2.3 vs 2.2.4) didn't fix this. To me, it's more likely with a new install, things might not be taking the same code path (maybe based on app settings?) so the problem is still there.
If users are reporting f5 problems, is the f5 family about the only CIQ 2.x devices you support? For example, if you only supported things like the f3, f3hr, and similar in the past, and not the va-hr or 735. It might be that 2.x VM is a bit stricter on a few things. Are you seeing an error like the other user with an error in the number of arguments?
As an update:
I just published a watch face that is working without problems on F3, Forerunners and VAHR.
It works perfectly on my F5.
But I got a feedback from a user that it does not work on F5X.
I asked the user to send me the CIQ-log file. But he reported that the LOGS folder is empty ...
In case there is anybody who owns a F5X could test the face and give me a feedback would be helpful.
Cool, love Garmin. Not a single release without major bug.
Here is what users reporting:
"Froze my 5x as well. Was able to recover without reset. 5x was still connected to GC on IOS and I was able to install a new watchface. Then restarted the watch by pressing Light for 10 seconds and starting again. Watch then loaded the new watchface and I could delete this one. Hope that my help others who get hit by this... "
"Freeze the 5X!! Factory reset!"
"One of the best faces I have tried, but it chrashing on Fenix 5x "Loading Watch Face" freeze.... Please fix it ;) "
Thanks to your help I was able to reproduce some of these errors. It looks like there is something going on with the integration on the 5X. I have no problem running Rugged Analog on the fenix 5. They both should work the same, but I'm getting the very odd crash with no logs on the 5X. I've pushed all the info I have to the device team about the issue and will keep you all updated as I know more.
Thanks!
So I just removed the support for F5X for my watch faces, until there is a solution to this problem.
In case you need my source code, just contact me.
Thanks to your help I was able to reproduce some of these errors. It looks like there is something going on with the integration on the 5X. I have no problem running Rugged Analog on the fenix 5. They both should work the same, but I'm getting the very odd crash with no logs on the 5X. I've pushed all the info I have to the device team about the issue and will keep you all updated as I know more.
Thanks Coleman! Please take a look at GigicWatch face too, if by any chance the issue is different. Unfortunately I have no 5X to test.
