RESOLVED: "Unknown caller" calls with Android 9.0

[AlessFitbit]

Fitbit Update: 9/6

Everyone, please make sure you are enabling the Fitbit app permissions under Settings of your Android device. You can go to Settings > Apps> Fitbit app > Permissions and make sure you have it toggled on. 

Since I've received confirmation that this has been resolved with the latest update to the Fitbit app, version 2.78, I will be closing this thread. If you come across this issue in a future instance, please create a new topic on the forum and reference this one as the issue. Thanks for all your patience as we worked to get this resolved. 

---

Fitbit Update: 9/5

Hi, everyone - Yesterday on 9/4, we started the release of the Fitbit for Android app version - 2.78. As with all our Android app releases, it is a slow and gradual release until it is completely out to everyone. You should all see it available sometime this week. Once its available to you, you'll be able to download it from the Google Play store.

This app version contains fixes and improvements for calls being received as "Unknown Caller." So please download it once you see it available and let me know here in this thread how it goes. I really appreciate everyone's patience! I'll stick around to hear some confirmations that the fix worked.

---

Fitbit Update 08/22/2018: Hi, everyone!

I wanted to let you know our team is aware that some of you are seeing "Unknown caller" on your Versa/Ionic watches since updating to Android Pie (9.0).

They are already investigating the issue and I will let you know when a fix is available. Thanks for reporting this here on the Community. 

[Grimmbold]

Well, remember If you bought your FitBit from Amazon: Call them - if FitBit does not offer a solution, Amazon will refund the watch and reclaim it from FitBit. Did so with my Samsung Gear, where Samsung refuses to shed an Update, and will do so with my Versa end of the week, if no fix.

As the word goes: Its fun, untill too many customers call Amazon - then it gets hilarious!

[MarinaCarbo]

Exactly the same problem for me - Versa with Pixel 2 XL. Tried everything and nothing solves it. I hope they fix this issue soon.

[Grimmbold]

Well, I got a change now - no caller at all. 
Watch goes back to Amazon - Garmin here I come!
See you guys...

[SunsetRunner]

Surprise surprise! I have a Pixel 2 XL running Pie and a Versa and guess what?!?!..... I have exactly the same issue! Adding my voice to the issue to hopefully kick Fitbit into action. Should not be a major problem to fix, you'd a thunk!

[dluu]

I wanted to join this party train so I jumped on. Pixel XL 2 and Blaze here. Reporting the same issue: when someone calls, I see "unknown caller" on my watch but the name and number shows up on my phone. I've tried restarting my fitbit, uninstalling and reinstalling the Fitbit app but nothing works.

[AlessFitbit · Accepted solution]

Fitbit Update: 9/5

Hi, everyone!

Yesterday on 9/4, we started the release of the Fitbit for Android app version - 2.78. As with all our Android app releases, it is a slow and gradual release until it is completely out to everyone. You should all see it available sometime this week. Once its available to you, you'll be able to download it from the Google Play store. 

This app version contains fixes and improvements for calls being received as "Unknown Caller." So please download it once you see it available and let me know here in this thread how it goes. 

I really appreciate everyone's patience! I'll stick around to hear some confirmations that the fix worked. 

[Grimmbold]

No option for Download and or Upgrade yet

[Grimmbold]

Seriously? "The update is available to 10% of the Android Users for testing purposes and will be rolled for all users soon!" (Quote Support).

[Phil_R]

Dude. Take a Xanax. They're rolling it out. We've all said our piece to get there attention, now we just have to wait for the update.

[Grimmbold]

"Dude", time is a matter, if you have so-and-so-much-days - either to return the product or keep it. And given the fact, that FB already stretched their mark a bit, by first saying that its due device compatibility, then resorting to the sterotypical "do-a-hard-reset-even-though-it-wont-do-aything-but-delay" solution and than finaly admitting, that they overlooked 8 months of A9P beta, its a bit of a non-smooth move, to announce a rollout, when it is just out for the testers - especially since the board messages paint a picture, that the last rollouts where also banana rollouts, software growing with the users...

[mwd055]

Just downloaded the new update and still showing unknown caller. I made sure the app synced with the watch and rebooted both phone and watch. Still getting unknown caller.

[bokonon]

I just got the update and it fixed the problem.  Make sure to grant the fitbit app the Access Call Logs permission.  It won't work without that permission.

[mwd055]

Thank you!! That worked

[danshawna]

After update and restarting both devices and making sure permissions are set up "unknown caller" is still coming up.  Please fix this Fitbit.

[Jerry1H]

Just received the new update from the Google Play Store and it solved the valet ID issue! It seemed to show up in Google Play after a new Android 9 update popped up today (Pixel 2 XL). Anyways, had to enable access to caller logs. 

[Stealjamnow]

Downloaded latest now call notification not working at all. Test call notification not working. App cache cleared as with all permissions, uninstalled and reinstalled. Reset tracker, reset Bluetooth. Still not working. Update seems to have made it worse

[AlessFitbit]

@bokonon @Jerry1H Thanks for confirming that the Android app version 2.78 has resolved this caller ID issue on Android Pie (9.0). 

Everyone, please make sure you are enabling the Fitbit app permissions under Settings of your Android device. You can go to Settings > Apps> Fitbit app > Permissions and make sure you have it toggled on. 

Since I've received confirmation that this has been resolved with the latest update to the Fitbit app, version 2.78, I will be closing this thread. If you come across this issue in a future instance, please create a new topic on the forum and reference this one as the issue. Thanks for all your patience as we worked to get this resolved.