Widget crashes the entire watch

Hi,

I currently have a problem that my widget let crash the entire watch. It stucks at the splash screen. A hard reset helps temporarily. I am wondering how this can happen? Any hints?

jim_m_58 over 5 years ago in reply to topcaser

Looks to me that should do it.

topcaser over 5 years ago in reply to jim_m_58

Maybe you want to address this problem in your blog post Jim

sabeard over 5 years ago in reply to topcaser

Glad to see you solved your issue. In my case I have no background service to deal with and it can reliability be triggered after saving settings with the ConnectIQ app. The only did is to restart the watch and reinstall the app and save settings with GCM.

jim_m_58 over 5 years ago in reply to topcaser

This strikes me more of a bug than something to document, as it could be other things in onBackgroundData() could cause this this too. Crashing the entire watch is a really bad bug. Travis.ConnectIQ?

Travis.ConnectIQ over 5 years ago in reply to jim_m_58

Yes, crashing the device is a huge no-no. We will need to look into that.

That said, it seems the solution to be sure that batData was initialized shouldn't require an additional variable. Just checking batData for null should be sufficient to tell if it had been initialized or not.

topcaser over 5 years ago in reply to Travis.ConnectIQ

OK I'll rewrite the code. I'll save one variable which is not loaded in the background service making it more compact