Modifying settings on side loaded app

It's not possible to set app settings of a side loaded app from GCM or GE. What you can do is copy the simulators setting file from your computer to the /garmin/apps/settings folder on your device.

Hi,

So does it mean we have to trust that it will work when we release the application/datafield ?

I guess by copying the settings file should do the trick, allowing us to test on a real device... But I do hope Garmin will include this feature in their to-do list, as it helps developers to properly test their apps, and have confidence that it will work when published.

Thanks,
JF

It's not possible to set app settings of a side loaded app from GCM or GE. What you can do is copy the simulators setting file from your computer to the /garmin/apps/settings folder on your device.

Not very intuitive... The simulator saves the settings on a temp directory, located on the folder reported by the java java.io.tmpdir system property.

On Mac OS, you can try:

find /var/folders/ -name SETTINGS 2> /dev/null

to find it.


On windows, it's probably located under the directory reported by the %TEMP% environment variable.


Regards,
JF

The app store was meant to allow developers to test app settings with submitted but not yet approved apps. This is broken at the moment and is being investigated by the store team. Hopefully we'll have a fix soon!

The app store was meant to allow developers to test app settings with submitted but not yet approved apps. This is broken at the moment and is being investigated by the store team. Hopefully we'll have a fix soon!

But this is only half the solution.

Let's say someone had a "version 1" of something in the store, and it's already been approved and download by users.

If they develop a "version 2" that now has user settings, and they update the version in the store, it's there for users right away (no waiting for "Garmin approval" involved)

What if the store not only waited for "Garmin approval", but also "developer approval" (which the developer can optionally clear on a new update) before it was available to the public? They store would still have version 1 available until the developer approved version 2 in the above example.

I totally agree with jim_m_58, I was surprised that for an update of the application, it was directly visible for download.

A "Publish application"/"Developer approval" option should be available to let the developer test the new version.

What Jim has described is kind of a next phase feature that's under design. We're considering a beta feature, that will allow developers to upload beta versions to the store without replacing the currently released version. I've requested that developers have the ability to selectively give access to beta users, but I'm not sure whether that will be implemented.

I don't have any details to share right now, but I know that we do want to add features that fit what you're describing. :D

old post, but for me the settings file in windows was under

C:\Users\[username]\AppData\Local\Temp\GARMIN\APPS\SETTINGS

it's named [appname].set