Limitations in number or size of settings?

Former Member over 8 years ago

Is there a limit in the number of settings of the size of all the settings data that I am not aware of?

It seems as I am adding configurable settings to my app/watch face, I'm finding all kinds of strange things happening.

My last stable build had 31 configurable settings, and everything worked fine in the simulator, and the App Settings Editor.

After adding a few more settings, I now see several problems:

- From the App Settings Editor, Eclipse has reported a null reference exception, I can't load any settings at all now in the App Settings Editor
- If I remove a few, I can load the settings, but if I try changing any in the App Settings Editor, they do not save and are not sent to the simulator.

I'm guessing there is either a bug somewhere, or an undocumented number of settings or size of the settings data that I am not aware of.

The settings still seem to work fine after I publish my app/watchface, but I am no longer able to test anything before publishing, which makes it really inconvenient.

travis.vitek over 8 years ago

Is there a limit in the number of settings of the size of all the settings data that I am not aware of?

Yes.

I'm guessing there is either a bug somewhere, or an undocumented number of settings or size of the settings data that I am not aware of.

It is documented. There is a limit of 8K for the total size of the properties data. Have a look here.

The settings still seem to work fine after I publish my app/watchface, but I am no longer able to test anything before publishing, which makes it really inconvenient.

As mentioned many times before, you can upload your app with DO NOT PUBLISH in the description, and you can test to your hearts content. If you've already published, you can still test using the same technique...

Rename your existing manifest.xml to manifest.xml.release. This is the manifest file you'll use when you want to update the public version of your app. Copy manifest.xml.release to manifest.xml.testing. Generate a new application id and update the value in the manifest.xml.testing. This is the manifest file you'll want to use when you want to update the test version of your app.

Now that you have the two files, and they have unique application ids, copy manifest.xml.testing to manifest.xml. Build the app for uploading to the store, and upload it. Be sure to put DO NOT PUBLISH in the description. Once you've completed your testing, copy manifest.xml.release to manifest.xml, build a distributable, and upload to overwrite your published version.

If you need to test a new version, do the same thing. Copy manifest.xml.testing to manifest.xml, build, upload, test..

Travis