Simulator not responding

I'm running into this issue way too frequently now.

When I click on Run, simulator starts with the big blue triangle, nothing is shown in the console and the simulator window goes into Not responding state. I have to kill it.
Then I have to choose another run configuration which just starts a sample app from Garmin, click on Run->blue triangle->not responding->kill.
Click on run again->sample app starts without issue.
Change the run configuration back to my watchface, click on run, watchface starts without issue.

Then if the companion app sends a message back to the simulator, simulator goes into the Not responding state immediately.

This did not happen that regularly before and I don't know what causes it. Either the upgrade to SDK 2.4.1, using the new Store.getValue/setValue, or making a bunch of new settings which pushed the memory usage up to 75.1/92.1kB.

Any ideas?

Former Member over 7 years ago

Hey,

I've got a ticket created to investigate this. Is there any way I could get you to send me a reproducible test case to [email][email protected][/email]?

Thanks,
-Coleman

DEXTER over 7 years ago

Hi!

That's the issue though. I cannot pinpoint out what's causing it so I cannot create a reproducible test case. I can give you part of my watchface code to show what I'm doing in the background service, or I can also give you the full code of it, but you'd still need a companion app to send messages back to the watchface (and I don't want to write a whole new companion app for just that).
So what do you suggest?

Former Member over 7 years ago

Would you be willing to post what version of eclipse you are using, and what operating system? Are you using the 2.4.1 eclipse plugin as well?

DEXTER over 7 years ago

Sure. Win10 - Neon 4.6.0.
I've also tried it out with Oxygen - 4.7.1a and also got the Not responding error. I'm not surprised though since the simulator.exe is a completely separate process so it shouldn't matter which eclipse version I'm using I assume.
Yes, 2.4.1 eclipse plugin too.

DEXTER over 7 years ago

Coleman.ConnectIQ I think I found out what's going on and I've already lost 50% of my remaining hair (and I didn't have much to start with)
So first, see this bug I was explaining to Brian.ConnectIQ : https://forums.garmin.com/forum/developers/connect-iq/connect-iq-bug-reports/1274768-transmit-in-backgroundservice-only-happens-in-every-other-cases?p=1274828#post1274828

I had a sudden idea of moving the registerForPhoneAppMessages call back from after the transmit to BackgoundServiceDelegate::initialize and lo and behold the simulator freezing just stopped!

This means at least 2 thing:
- I really don't want to believe that I'm the only one using background messaging but it seems so
- The developers are not testing the background messaging feature at all, or not very thoroughly

Please update your internal ticket with this new info. Thank you.

Former Member over 7 years ago

DEXTER,

Thank you for the rest of the information here. I've updated the ticket with the new info. We will look to see if this is a secondary bug that is causing the issue described here or if this is really just a symptom of the issue described in you first topic thread. The background messaging feature is tested with each SDK release, though it appears that there are a some use cases that are missed. When we come across gaps in our testing procedures that are revealed by unique use cases by our developers we try to bring those cases into our testing in a realistic manner. Thank you so much for helping us make Connect IQ a better platform!

-Coleman

Former Member over 7 years ago

This has been fixed in version 2.4.2. If this fix does not cover your use case, please create a new thread with reproduction steps and we'll take a look as time permits thank you.