App log file

That's another issue.  You really want to uninstall the store version before you copy over a sideload.  What's happening is caused by two apps with the same ID in the manifest.  And with the sideload, you many want to make sure it's not a release build so you have debug symbols.

Thanks Jim, yeah the sideloads were not releasebuilds. But my debuggin skills are as advanced as looking at which System print line it failed at   If I get to the stage i need to use debugging symbols... all downhill from there

What it will do for you is that when you get a ciq_log file, the stack trace will use the symbols, so you'll see line numbers in the code, etc.  It's really the easiest way to see where a problem occurs.

Ahh, I was using that without realizing it already...

Thanks!  

Problem now fixed

I'm trying to figure this out. After sideloading an app, it disappears from \GARMIN\APPS  so how do I figure out what the PRG file was renamed to ?

You can open the garmin\GarminDevice.xml file.  Near the bottom of the file you will find the xml entry for each app.  The app name will be listed along with an entry for the file name.

Or check the date it was last modified

On some devices, the prg files for some app types get moved and hidden.  garmindevice.xml is needed in that case.

I tried looking at that xml file, and my side loaded app doesn't appear in the file.  I confirmed that app is loaded and runs so it is on the watch somewhere.

trudelta said:

I tried looking at that xml file, and my side loaded app doesn't appear in the file.  I confirmed that app is loaded and runs so it is on the watch somewhere.

You could try introducing a deliberate error in your app, such as an out-of-bounds array access. Hopefully the app filename will show up in the crash log.