"Connecting to Companion" with no codes

[Icy13]

Been fighting this app for a couple days. Sometimes correctly formatted entries sync, sometimes they don't. Sometimes the codes load, sometimes I get a white screen with "Connecting to Companion".

I've tried restarting phone and restarting watch. However, once the keys are on the watch, shouldn't it be standalone? What is Companion?

Help! (former pebbler really hoping fitbit can finally succeed my steel; screen is so nice but the apps and OS seem very og pebble level reliability (aka alpha test)).

[Lixxia]

Hi there, are you still experiencing this issue?

[Icy13]

I have not seen it recently although I did have to uninstall and reinstall the watch app back when I sent the bug.

I also recently noticed that one of my codes was showing the wrong output (I have it in two authenticators) but the other 3 codes (also in both authenticators) were fine. I fixed the broken one and all seems well but no idea how it broke when the others didn't.

And I realize this isn't an open-ended feature request location, but a night/power save mode with white writing on a black screen would be highly appreciated.

Finally, the most maddening problem I had with the app (which is otherwise an excellent and useful tool) is that codes only send to the watch when the screen is on, app is open, and "Always on Display" is deactivated (not strictly necessary, but otherwise screen times out). This means you have to take the watch off and set it on a desk (to avoid wrist rotate screen blanking) after setting display to 60sec timeout AND still hurry to swap back to the app and send codes. Not sure if there is a fix for this but should definitely be explained in the instructions as it drove me insane trying to figure out for my first 3 days of ownership.

On Tue, Mar 3, 2020 at 6:04 PM Laura Barber [email protected] wrote:

Hi there, are you still experiencing this issue?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Lixxia/fitbit-authenticator/issues/16?email_source=notifications&email_token=ADFNK4XGCSIWW44XH6JDXODRFWZJNA5CNFSM4KBSERG2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENV7L7A#issuecomment-594277884, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADFNK4XNCTH42RAWVLL52ATRFWZJNANCNFSM4KBSERGQ .

[Lixxia]

Hm, if the output was wrong it was probably just a typo in the secret itself during input.

I'll open a ticket for the night-mode feature request!

The code sending issue is odd, there's definitely some weird stuff going on with fitbit's connection between the watch and the app. They're also deactivating the app's ability to use Always On Display with the newest version so I'll take another look at it and see if I can pin down some clearer instructions.

Thanks for the feedback!

[jecxjo]

Seeing the same issue. At first was seeing the "No Codes/Please Add" display and the other settings were transferred just fine (timer color, font, etc). But after resetting my watch and killing the mobile app I did notice that the mobile app completed changed its UI (now a slider on the top to pick my phone, watch faces or apps). Think there may be some UI updates that are semi-automatic on the mobile side, not quite sure how that all occurred purely in killing the app.

But after all that I'm now on the same "Connecting to Companion" screen.