forked from hasscontrol/hasscontrol
-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
cannot exit screen: 'Failed, Phone not connected'. #31
Comments
unfortunately, I can't reproduce the issue. |
Yes, it is still happening. I tested by disabling bluetooth on mobile,
navigating on my Forerunner 255S music to the hasscontrol app where it
immediately sais 'Failed, Phone not connected'. The Back button, as well as
all other buttons cannot get me out of that screen. However, after waiting
for [what seems like] 120 seconds, the app automatically exits.
…On Tue, Aug 29, 2023 at 9:03 PM hatl ***@***.***> wrote:
unfortunately, I can't reproduce the issue.
is this still happening?
—
Reply to this email directly, view it on GitHub
<#31 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AF5T43GSGX5CERAHF73NFGTXXY4IBANCNFSM6AAAAAA2RKUEO4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Came here to report this, issue still exists, fenix 7X pro sapphire, latest os, and app release. |
fixed in v1.2.0 (verified in simulator) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When opening HassControll via the glance, and the device is not connected we see the error 'Failed, Phone not connected'.
It is not possible to leave this errorscreen when the phone remains unconnected. The back button brings the user back to the entities where upon loading the app notices the phone is not connected, showing the errorscreen and a loop is born.
Tested on Forerunner 255S.
The text was updated successfully, but these errors were encountered: