App settings editor causes eclipse to crash

Hi,

using latest SDK and eclipse plugins. This is my properties, which used to work. I have not changed ANYTHING, now when I try and load the app settings editor and select my app I get a spinning wait icon and eclipse is completely frozen so I have to kill it.

Any ideas!?!!?

<resources>

<properties>
<property id="PROP_DATE" type="number">1</property>
<property id="PROP_DATE_FORMAT" type="number">1</property>
<property id="PROP_DAY" type="number">1</property>
</properties>

<strings>
<string id="title_date1">Day / Month</string>
<string id="opt_date1_0">Day Month</string>
<string id="opt_date1_1">Month Day</string>

<string id="title_date2">Date format</string>
<string id="opt_date2_num">Numeric</string>
<string id="opt_date2_txt">Text</string>

<string id="title_date3">Show day</string>
<string id="opt_date3_no">No</string>
<string id="opt_date3_yes">Yes</string>

</strings>

<settings>
<setting propertyKey="@Properties.PROP_DATE" title="@Strings.title_date1">
<settingConfig type="list">
<listEntry value="0">@Strings.opt_date1_0</listEntry>
<listEntry value="1">@Strings.opt_date1_1</listEntry>
</settingConfig>
</setting>

<setting propertyKey="@Properties.PROP_DATE_FORMAT" title="@Strings.title_date2">
<settingConfig type="list">
<listEntry value="0">@Strings.opt_date2_num</listEntry>
<listEntry value="1">@Strings.opt_date2_txt</listEntry>
</settingConfig>
</setting>

<setting propertyKey="@Properties.PROP_DAY" title="@Strings.title_date3">
<settingConfig type="list">
<listEntry value="0">@Strings.opt_date3_no</listEntry>
<listEntry value="1">@Strings.opt_date3_yes</listEntry>
</settingConfig>
</setting>

</settings>

</resources>

Brandon.ConnectIQ over 9 years ago

I'm seeing this same thing under some circumstances, but I haven't yet singled out the precise conditions under which this occurs. It's under investigation, however, and we'll get it fixed. If there's something more specific I can tell you to do in the meantime, I'll post back here.

HermoT over 9 years ago

Have you tried deleting the SET file from your temp folder?
Maybe it is corrupt?

Brandon.ConnectIQ over 9 years ago

This appeared to be happening to me either when I used the simple watch app with settings template, or when I selected English as the supported language, but I was unable to conclusively determine the cause. I switched work spaces in Eclipse to work on another issue earlier, and since then, I have not seen the problem occur. I've tried several different app template and language combinations, plus tried editing app settings while the simulator was closed, open and not running an app, and open while running an app.

@RUPERTHAWKES: Are you still encountering this issue? If so, is it only occurring with a particular app, or all apps? Can you reproduce it with a new app?

ruperthawkes over 9 years ago

This appeared to be happening to me either when I used the simple watch app with settings template, or when I selected English as the supported language, but I was unable to conclusively determine the cause. I switched work spaces in Eclipse to work on another issue earlier, and since then, I have not seen the problem occur. I've tried several different app template and language combinations, plus tried editing app settings while the simulator was closed, open and not running an app, and open while running an app.

@RUPERTHAWKES: Are you still encountering this issue? If so, is it only occurring with a particular app, or all apps? Can you reproduce it with a new app?

Hard to reproduce at will. But it's just done it again! ie I select my watchface and it hangs eclipse. GGRR!

Now where is that set file exactly? on a mac

Brandon.ConnectIQ over 9 years ago

As I had mentioned, I was seeing this same problem on my Windows machine briefly, until I switched to a new workspace in Eclipse. I have since not been able to reproduce this on either Windows or Mac, but I reported it for investigation anyway since there is definitely some kind of issue here.

Thanks for the report!

Brandon.ConnectIQ over 8 years ago

We haven't managed to reproduce this issue, and since we haven't had any new reports of this for a while, we're going to consider the issue resolved. If anyone encounters this again, please start a new thread. Thanks!