Debug Logging not working on ForeRunner 935

Hi,

I'm having some trouble with a single user of my app who has a 935. The app will not write to the debug log, but I cannot figure out why (and I have a problem I need to debug).

The Log is in APPS/LOGS/<APPNAME_SAMECASE>.TXT and the app is in /APPS/<APPNAME_SAMECASE>.prg

This works fine on my Vivoactive 3 when I build exactly the same code and deploy it. I get plenty of logs.

I ran a Zoom session to eyeball what he's doing, and unless we're both blind it's exactly the same name TXT file to the app name, but it never changes from 0 bytes.

Has anyone else experienced this, or has any ideas of other things to try. The app runs enough that it should definitely generate a large number of logs.

Would resetting the watch, or changing something about the build help? (I built it in both debug mode, and not)

The app runs fine on the 935 simulator.

Appreciate any ideas someone might have

jim_m_58 over 4 years ago

You sent a sideload and it's not been installed from the store, correct? If it had been insattled from the store, have them uninstall the store version, then copy the sideload.

When an app is installed from the store, the name is a store generated 8 char string and that's the name that must be used for on device logging.

Dresbo over 4 years ago in reply to jim_m_58

Correct, yes. I haven't put it on the store yet as I'm sanity checking it on few devices before I do. (More accurately, it is there, but not approved and is marked Beta).

Dresbo over 4 years ago

For anyone else stuck this way, I worked around it by creating a REST endpoint I could have the watch POST logs to using the makeWebRequestAPI. This seems to work for my purposes, but clearly won't scale as an everyday thing.

I still have no idea how to get the watch to print out logs to the log file.

Travis.ConnectIQ over 4 years ago

I don't know of anything that would cause this behavior. I know there are limitations to the logging functionality (it is disabled temporarily during partial updates in watch face apps), but nothing that would disable logging entirely.

It might be helpful if you could provide the information on the firmware version of the device and maybe if this is an APAC or WW (Asia/Pacific or World Wide) device since the firmware can be slightly different.

Dresbo over 4 years ago in reply to Travis.ConnectIQ

Firmware version is 21.00. Ciq version 3.1.8. It should be a worldwide version since we're In Europe but not sure how we can tell.

Interestingly the app issue I was having on this watch still persists with a version that works fine on another watch of the same model. Having logs would be a big help but not sure of a way forwards other than my slightly flakey attempt to post logs to a Web service.

Does the log file extension need to be upper/lowercase. Does it matter?

jim_m_58 over 4 years ago in reply to Dresbo

I'm pretty sure you want to use upper case for the TXT.

FlowState over 4 years ago in reply to jim_m_58

It doesn't make a difference for me (935).

jim_m_58 over 4 years ago in reply to FlowState

Depends on the device. Older devices the name can be all upper or lower case, newer devices, the first part needs to match the case of the prg file.

on some devices, it also needed to be an 8.3 file name

Travis.ConnectIQ over 4 years ago in reply to Dresbo

Dresbo said:
Does the log file extension need to be upper/lowercase. Does it matter?

It technically depends on the underlying filesystem used by the watch. Usually it is FAT, so case does not matter. I've got in the habit of copy/pasting the file name from the PRG file and then adding an uppercase TXT.

Dresbo over 4 years ago in reply to Travis.ConnectIQ

I've asked the user to try it with a range of different casings and renaming the .prg file to app.prg in case that makes a difference.

I've also asked them to add log files for the other garmin apps they have to see if those ones can log.

This should at least tell me whether it's a problem with the watch or with my app.