Express leaves App unavailable, not shown in app list, possibly corrupting settings... serious problems with Express

Hello Brandon,

It has been 5 months since I first posted a description of this problem.

I have been avoiding using Express with my 245M because of this problem.

Express has gone through a couple of updates since I last tried it so today I decided to be brave and see if this problem has been fixed.

It has not.

I uploaded a new version of my app to Connect and selected the 245M for download.

Plugged the watch in to my computer and ran Express.

Express loaded the updated app into the watch.

Before disconnecting the watch I used Express to set one of the Settings for the app.

Then I disconnected the 245 and went to the app list to run the app.

As before, the app, which had been at the top of my favorites list was nowhere in the app list.

I connected the 245M to my computer again but did not run Express.

I found a new program file with the appropriate date and time so I assumed it was my app update.

I decided to power off the watch and power it on again to see if the app would appear.

It did. Not in the favorites list, but it was available in the app list. I moved it back to the top of the favorites list.

Is anyone looking into this ?

Today is the first time I've updated my app on my 245m since posting this error report. I made the mistake of using Express to update the app and once again the problem occurred.

After Express reported that it had completed Syncing, it indicated that it had lost communication with the watch. It never recovered, and the app wasn't available on the watch.

Using Connect I had to reload the app. All settings were gone.

I set a basic setting using Connect. It worked fine.

I reconnected to Express and set the same basic setting. It reported that it lost connection with the watch AND THE APP WAS GONE AGAIN along with all settings.

This is a real problem and burns a LOT of time.

It essentially makes Express unusable.

Is this not a problem for others ?

Is it related to testing of an unreleased app ?

I found a work-around for the problem of Express corrupting Settings. That problem is real and reproducible on the 245M and the VAHR. Express mishandles read-only fields in the settings so that the app involved crashes at runtime. Connect handles Settings so that this problem does not occur. I have described that elsewhere.

So... Express has two severe problems.

I have asked the project team for an update on the issue. 

This continues to be a problem and is a LARGE problem.

If Express connects with the 245M my app is removed along with all of it's settings.

This app relies heavily on settings so cut & paste to enter settings is important.

Currently the only reliable way I have of entering settings is through the iOS Connect app.

If I plug my watch into my laptop and run Express, the app and it's settings GO AWAY.... even if I don't look at or change any settings.

Please tell me when this will be fixed.

Are there other users reporting this SIGNIFICANT PROBLEM with their 245M or other watches ?

Is it only a problem with apps that have not been made public ??

This is a real hinderance for me.

Please find and fix this problem.

Thanks

Jeff

Reconfirmed.

After settings are changed in Connect, everything works.

After settings are changed in Express, the app crashes on startup with an "Unhandled Exception"  from a Properties.setValue() call.

Use Connect again, change a setting and save... the app runs as expected.

It's pretty clear that Express is mishandling Properties and corrupting something in the process.

Unfortunately CIQ_LOG doesn't indicate the exception being thrown though it doesn't much matter since it's the result of Express mishandling settings, not a problem in my Properties file, or Settings file, or misspelled keys etc...

The app also runs in the Simulator without a problem, and the App Settings Editor accesses, displays and sets settings as expected.