Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

no app connection available - but watch connected - find my phone fails

ziopaper
over 1 year ago

Hello,

I am not sure how common this is but it seems that everytime I need to use the watch to find the phone, I get a "no app connection available" when clicking on find phone

What doesn't make sense to me is that if I receive a phone call, the watch vibrates and I can answer so it is obviously connected. 

If I open the app, then find my phone works correctly. 

But basically I can't rely on it since whenever I need it, it has this issue

Anybody else with the same problem? What is a solution or workaround that you have been implemented?

thank you

  • 0 over 1 year ago

    What sort of phone (Apple, Android)?

  • 0 over 1 year ago

    Hi, sometimes it happens to me (iPhone, latest iOS). Workaround for me is to shut down connect (swipe it out of the screen) and launch it again.

  • 0 over 1 year ago in reply to nowster

    iphone, latest OS

  • 0 over 1 year ago in reply to sbiker_Pavel-CZ

    yes, that works. But I need that not to be needed because that voids the point of "find my phone". Because you need to have the phone to re-launch Connect

    The weird thing is that I would receive phone call notifications on the watch, so it is obviously connected 

  • 0 over 1 year ago in reply to ziopaper

    I just tested. Seems to fail if you kill Connect on the phone manually. Even if it has permission to update in the background. However, I have not experienced problem in real life, even with update background disabled. But it does have access to location services set to always, which might keep it alive, unless it is killed manually.

    Notification access is a Bluetooth setting, so phone calls etc., does not require Connect running.

  • 0 over 1 year ago in reply to PallMe

    thank you. I changed the location permission to always but it seem to have no change

    So if you kill connect manually, you can still receive calls to the watch it seems.

    Don't see why find my phone wound't still work. I tested killing Connect manually like you said and confirmed, it behave identical to the issue I am having. In general I never kill Connect so not sure what causes it

    The problem is when this fails me when I need it the most to find the phone...

    have you seen this before?

    thank you

  • 0 over 1 year ago in reply to ziopaper

    Some features, like Find My Phone, will not work with iOS devices if the Connect app is force-closed. Please see Some Garmin Connect App Features Are Not Working On My iOS Device for more information.

  • 0 over 1 year ago in reply to Garmin-Sierra

    Today I experienced it even though the Connect app was running. I recieved notifications from other apps and inside Connect it was green as connected. I didn’t try if sync was possible. I did a toggle off/on off BT on my Iphone in the control-center (doesn’t actually turn off bt, but disconnect devices) and find my phone from watch worked again. Seems like communication between connect and the watch was in stuck state. I don’t know if an app update 1-2 hours earlier (now running 4.76.0.23), caused this. I did run the app after the update, but didn’t check if the watch was still syncing.

  • 0 over 1 year ago in reply to Garmin-Sierra

    Hi 

    I never force close Connect, I was just experimenting and the behavior is the same

    I have not identified was causes it. When it happens, opening Connect fixes it, but the next day might be the same thing

     what else could I try?

     Thank you

  • 0 over 1 year ago in reply to ziopaper

    Check that Background App Refresh is enabled and Low Power Mode disabled, like detailed in Sierra's link