Problems with .PRG files

Former Member
Former Member
I have uploaded my app to Connect IQ Store, it's approved, and I have installed my app in my devices to test it.
I have uninstalled it to continue developing new versions, but when I upload .prg files to/GARMIN/Apps/myapp.prg, myapp.prg disappears from /GARMIN/Apps/ and I can't see my log in /GARMIN/Apps/Logs/myapp.txt
any suggestions?
  • If name (app name, not file name) of downloaded app and copyed are the same, could be conflict. Remove downloaded from iq app, and continue your tests with prg))
  • It's not the name of the .prg or the name of the app that causes the conflict, it's the app ID in the manifest.xml file that causes the conflict. That's now the device identifies a .prg. By the ID.

    the .prg files are the compiled source code and resources. There is no source code in a prg file and once a .prg is built, you can't changed the app ID.
  • Well, although this thread is nearly one year old, since I have previously run into this problem myself, I will add:

    1) Yes, if a CIQ app is already installed from the store and you try to sideload the same app (with the same ID, as Jim pointed out), the watch (or is it Garmin Express) will automatically rename your PRG to the same kind of "random" string of letters and numbers that you see with apps installed from the store. I'm not sure how consistently this happens, but I've def seen it before.

    2) If you uninstall said store app before sideloading your private build, the sideloaded filename should be preserved afaik. I just tried it with an app of my own, and it seemed to work fine. If not, I can only suggest manually editing \garmin\devices.xml on the watch to remove any references to the app.

    I will also add that it's probably best to limit the filename and extension to the old "8.3" format (no more than 8 characters for the name, not including the .PRG extension). I understand some watches may have no problem with longer names, but I def have issues on my 935 with longer names.
  • Things are a bit different if you have installed from the store and then copy a side load vs a sideload and then install from the store, as far as what name is used. the name also IDs things like the setting and storage files, and if they are preserved. But I can't recall the specifics of which is which.

    The best bet is to uninstall the store version if you want to run a sideload, or uninstall the sideload if you want to install a store build.