Autom. Screenlock calls onHide (no simulator support)

Hello everyone,
I got a review, which says:

Your app stops working, when the automatic screenlock is activated

The only thing, I can imagine is the onHide()-Event, which stops my timer. It should be called when a Menu appears or you want to move to the widgets (which is not possible, but I hoped so in the past).
I can easily solve it by removing the onHide and stop my timer in onMenu.

But in my eyes the screenlock should not "Hide" the app. It should be active, still!
And there should be a possibility to simulate this in the simulator. Maybe not automatically, but like "force onHide" and "force onShow".

Using onHide, hides the GUI. And the unlock-button still works as an app-button. It is not a proper way to simulate it.

Former Member over 8 years ago

HerrRiebmann ,

I don't think this is the behavior we want. Generally Connect IQ should not be interrupted by any native views on the the device. I've created a ticket to investigate.

Update: I was able to reproduce this. There is no crash. Your timer just pauses when the autolock happens. I'm going to run this by the team and see if this is an integration issues or if this is intended. It may be that there is an event given to the VM when autolock is enabled that we didn't intend. We'll find out more and update you.

Thanks,
Coleman

Former Member over 8 years ago

The team has discussed this and determined no changes are needed and this is by design. Please reach out to us if there are further questions.