Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

App on watch cannot be exited when in a specific state #12

Closed
Artaud opened this issue Oct 16, 2018 · 9 comments
Closed

App on watch cannot be exited when in a specific state #12

Artaud opened this issue Oct 16, 2018 · 9 comments

Comments

@Artaud
Copy link
Collaborator

Artaud commented Oct 16, 2018

Investigate: At some point the watch app will be stuck in "Stopping" state with no option to actually exit the app

@MrFly
Copy link

MrFly commented Oct 16, 2018

Noticed the same here with VA3. Sometimes I'm even not able to scroll, sometimes the screen keeps scrollable. I tried a bit (was able to open the shortcut menu) and noticed, that after "Stopping" was shown up, I was able to long press on the screen. After a time the "! CIQ" logo was shown and then I was able to use the "back" gesture to get back to the clock widget. Maybe this was a random behaviour, but I will try it next time it hangs...

@aaronjwood
Copy link

Is this for #4?

@MrFly
Copy link

MrFly commented Oct 17, 2018

No. :-)

@gcupic
Copy link

gcupic commented Oct 18, 2018

I can confirm the bug on Garmin Fenix 3hr combined with OnePlus 6 both running on fresh SW packages

@Artaud
Copy link
Collaborator Author

Artaud commented Nov 27, 2018

This is impossible to fix properly without a fix on the Garmin side (see https://forums.garmin.com/forum/developers/connect-iq/connect-iq-bug-reports/158068- )
I have pushed a workaround in b41852e

@Artaud Artaud closed this as completed Nov 27, 2018
@gcupic
Copy link

gcupic commented Nov 27, 2018

This is impossible to fix without a fix on the Garmin side (see https://forums.garmin.com/forum/developers/connect-iq/connect-iq-bug-reports/158068- )
I have pushed a workaround in b41852e

Hi,

will it be published in the Garmin Connect Store or we would need to sideload it somehow?

Thanks!

@Artaud
Copy link
Collaborator Author

Artaud commented Nov 27, 2018

I will publish it today or tomorrow.

@nmmacmillan
Copy link

:( picked up a VA4 today and I'm seeing this too. Anything I can do?

@gbossss
Copy link

gbossss commented Feb 1, 2020

Same here with VA4... Only workaround for me is to restart the watch...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants