My data field has experienced this several times. I'll make a minor change to the default values of a User Setting in properties.xml and re-publish my field. When I run it on my EDGE 1030, it actually runs, but the field is completely blank, visually. So strange. I knew if I deleted all the related files on the device, it would work. But this time I wanted to figure out WHICH file was the issue.
I first removed the .SET file. Still broken. Next I deleted the larger .DAT file. BOOM - the field worked! When I plugged it back in, both the .DAT and the .IDX files were missing. I hadn't hit START yet. Then I started the device and started an activity. At that point the .DAT and .IDX files were re-created.
So, for whatever reason, the .DAT file seems to cause a data field to fail following a properties.xml change? This field uses background processing to get the device temp. It also uses Storage.getValue() for persistent storage as part of the background logic. It uses Properties.getValue() to get the User Settings. I also use generic ANT methods to get TEMPE temps.
Does anyone know what the DAT/IDX files do? Anyone else experience this strange artifact triggered by a properties change?
I did notice the .DAT file I deleted was about 2.3KB, but the new one just re-created was 1KB. I only use Storage to save two values in the background process for device temp, so I wonder if this file slowly grows unbounded for some reason... adding an item every 5 minutes? Ugh.