restore to factory default

My problem is that my app works fine on my (VA-HR) watch, but crashes on my remote alpha tester's watch.
I suspect the issue is related to initial settings (somewhere...but where?).
I need to restore my watch to true factory settings, to replicate the issue, but when I take the Settings/System/Restore Defaults, I don't get that state.
My apps remain in GCM/Android as "NOT INSTALLED" and I suspect there are other remnants on the watch.

Has anyone had this issue and have any suggestions

Alan.raceQs over 8 years ago

Crash logs

Now you have shown me how to access crash logs....what do they mean????
Here are six examples from my alpha tester's system.

1.
ERROR: Unhandled Exception
DETAILS: `ý
STORE_ID: 00000000000000000000000000000000
CALLSTACK:
(the "`ý " in the 2nd line decodes to the following HEX string:
60 fd 07 20 11 01
)

2.
WARNING: failed inside handle_json_callback
STORE_ID: 00000000000000000000000000000000

3
ERROR: Unhandled Exception
DETAILS: Failed invoking <symbol>
STORE_ID: 00000000000000000000000000000000
CALLSTACK:

4
WARNING: Error in positioning callback
STORE_ID: 00000000000000000000000000000000

5
ERROR: Unhandled Exception
DETAILS: Failed invoking <symbol>
STORE_ID: 00000000000000000000000000000000
CALLSTACK:

6
WARNING: Error in positioning callback
STORE_ID: 00000000000000000000000000000000

2, 4 and 6 look like Warnings that I'll have to find a way to track down and handle in the code.

1,3 and 5 are hard crashes without meaningful log data.

After he restored his watch to "Defaults", it crashed twice further with error/warning identical to 1 and 2 and then they ceased and now the app runs fine!
But if my production users get these issues, my support line will never go quiet and my app will die from negative user reports.

So, serious? You betcha!

Coleman.Apps over 8 years ago

raceQs,

I have sent you an email about this issue.

Thanks,
-Coleman

Coleman.Apps over 8 years ago

I wanted to post here and let everyone know that I have created a ticket to investigate the cryptic error in the first unhandled exception.

Thanks,
-Coleman