Debugging without physical device

Former Member over 7 years ago

I just released a watch face for the VA3 and though publishing it for fenix 5 as well would be low hanging fruit. Everything worked fine on the simulator but shortly after publishing I got feedback from a user that it is not starting up on his device but reverting back to the standard watch face. It seems to run on the Vivoactive 3 (there I am also still waiting for my own device) even though the code does not distinguish between those two devices.

So I am wondering if there are any good ideas on how to approach these kind of bugs. Simulator works fine, device not and none is available to check yourself.
I cannot afford to buy each device just for testing.

Any best practices or typical reasons for these kind of bugs?

jim_m_58 over 7 years ago

First think would be to see if there is a CIQ_LOG.txt file on the watch and see if anything jumps out at you. If there's not much detail there, maybe send a debug build to the user and have them sideload it. Is it crashing on the va3 or the f5? (and is it an f5 vs a f5x) What FW version?

Details on when it crashes would be useful. Does it crash when it's the selected WF, but not in preview mode? Are you doing "always active" with onPartialUpdate()?

Former Member over 7 years ago

Hey Jim,

this is what I know:
Fenix 5X with FW6.
Selection preview is working.
But when it loads after selection it reverts to standard WF.
No onPartialUpdate.
VA3 seems to be running, at least I haven?t heard any complains yet, though I think the number of owners will be quite limited still - at least in Germany you cannot buy it yet.

I never thought of asking the user for a CIQ_log as I thought it to be too ?challenging? for the typical user. I will try that one.

jim_m_58 over 7 years ago

If your WF is in the app store, post a link. By the way, the last bit of FW numbers can be important. Today it's 6.00. The last digit being 0 indicates production FW, and non zero, beta. The Fenix folks like to release a bunch of beta versions :)

jim_m_58 over 7 years ago

That's just a link to the store but not your WF. What's the name of your watchface? I see Germon 3, but it doesn't have the f5x as a target.

Former Member over 7 years ago

Strange, the upper Link worked for me. It?s Germon 3. But I pulled it for the fenix 5X.

Former Member over 7 years ago

I will update it again with F5X support but that will not happen before Wednesday as before I do not have access to my development PC anymore

Former Member over 7 years ago

Ok, reintroduced fenix 5X support, handled some special condition, where a divisor could become zero. The user reporting the issue already reported back, that it is working now for him.
Jim, thanks for your support!