Inspire is getting text notifications with a verification code

[Tatania76]

Hi there I’ve got an inspire Fitbit connected to my IPhone XR but I’m continuously getting texts saying it’s a verification code?? Sometimes 3-4 times a day??? 

Moderator Edit: Clarified subject

[Tatania76]

Have you been getting constant texts with a verification code? 

[Tatania76]

I just panic that someone is hacking my account on the app and if they are what other things are they accessing as I had my bank hacked in March ..so why am I continuously getting texts with a verification code 🤷🏻‍:female_sign:..I’m not sure how to stop them and I can’t find info on it either,sooo annoying 😡

[SilviaFitbit]

@Tatania76 Welcome to the Fitbit Community. Thanks for the detailed information shared. 

It's odd what you're experiencing. I see where your concern is coming from. I moved your post to this board, in an effort to keep the forums organized. 

If you're getting this in a text message, you may want to double check the phone number where you're receiving it and check with your bank for security purposes.

Note that your Fitbit will display the notifications received from your phone. May I know if you set up the Two factor authentication on your Fitbit account? Every time you log in, you'll need to enter your password and the verification code sent to your phone. Learn more about it in this article. 

Hope this helps. 

[Tatania76]

I’ve received your reply by email and to clarify yes I have set up 2 bit authentication..I’ve also got a pink notice on this forum stating there is an issue with my Fitbit ‘we have identified an issue syncing your Fitbit and receiving notifications on your android phone’…

[SilviaFitbit]

@Tatania76 Thank you for getting back. Keep in mind that you'll receive this verification code every time you log into your Fitbit account. If you're receiving them even when you're not trying to log in, get in touch with our Support team, they'll be happy to continue assisting you. 

In regards to the Android syncing issue, you may want to try the workaround mentioned in the main thread. 

Hope this helps.