See message: com.fitbit.HTTP error 403 when attempting to setup

[KateFitbit]

Update: 12/22/2017: We released a new version of the app today which should resolve this issue. Please update your app. Thanks for your reports and patience. 

We received reports that an increased amount of users see Error 403 when attempting to set up or sync their device. If basic troubleshoots do not work (force quit app, restart tracker, restart device) users have reported uninstalling and reinstalling the app helps resolve the issue. 

Thanks very much for your reports as we work on a resolution. 

[DHoney1]

This was a really quick solution in transitioning to new iPhone 8+...!

[wcjacobs]

I switched phones and got the same error. I had transferred my apps from old phone to new using iCloud backup. Could not get it to sync properly. Uninstalling the app and reinstalling it worked for me. Just go through set up procedures again and your set.

[Bkread2]

Actually literally just updated and it still will not sync to either my flex 2 or charge 2 on the iOS app! No problem with my kindle fire though so clearly after 2 different patches in 2 days someone needs to get back to work!! Getting very frustrated! Since September no notifications either!! WTF?! Doesn’t make me want to upgrade to the Iconic! I have also tried every single suggestion too so not good at all!

[aculrich]

I tried everything, and then uninstalled and reinstalled the app, and it now works with my iPhone 8 Plus!!

[aculrich]

Uninstall and reinstall the app!!  I just did this, and it resynced to my new iPhone 8 Plus.  Good luck, and I hope this works for you!!

[aculrich]

Try to uninstall (delete) the app, and then reinstall it.  I just did this and it works with my new iPhone 8 Plus!  Good luck and I hope this helps.  This was SO frustrating!!

[stapert]

To sync my Blaze with  my new iPhone 8, i needed to delete my fitbit app, re-download it, then all was well.

[vegeloon]

I just got the iphoneX and uninstalling and re-installing the fitbit app worked for me.

[DawnCo]

My alta HR and iphone are not syncing. I've had no problems with it  for months but for some reason they now won't sync.  I tried turning blue tooth on and off and restarting the Alta HR.  But I kept getting a com.fitbit.http error 403.  So I deleted the device from my iphone and tried setting it up again.  I put in the 4 digit number that displays on my Alta but I still get the com.fitbit.http error 403

[Kev105]

Fitbit Blaze had error message with new Iphone 8 this week. Uninstalling & re-installing the App worked. 

[Bethmc1167]

Same thing happened when I got my new phone, so I just deleted the app and reinstalled the app and it works now.

[acooper]

Deleting the app and adding it back WORKED!   Thanks so much!

[BARTEKES]

I WOULD LIKE  A REFUND  !!!

ENTERING THE FOUR DIGITS AND THEN RECEVING 403 ERROR MESSAGE WILL NOT DO IT

[KateFitbit · Accepted solution]

Hi everyone, we released a new version of the app today which should resolve this issue. Please update your app. Thanks for your reports and patience! 

[EvHe]

Have uninstalled twice and now getting the networkbitkit error when trying to log in!! This has been going on for 2days now Ive had wifi on and off, restarted phone, blue tooth on and off and nothing. How can I connect my alta to my phone??

[aculrich]

This is very frustrating!!  My Flex 2 did sync with my iPhone 8, but only as much as allowing me to view and edit the dashboard.  I’m not getting text or phone notifications at all now, so I don’t know what is going on!!

[aculrich]

Now my Fitbit Flex 2 won’t receive text or phone call notifications from my iPhone 8 Plus. I can at least open the app and view the dashboard, but I don’t know why the notifications won’t work.

[WPaul]

Done that (updated app) but I still get the 403 error.  Got a new iPhone and can’t get the two devices to sync. Frustrating 

[WPaul]

Ok - deleting app and reloading the app and signing in again allowed to me to setup my Charge 2 on a new iPhone X with now errors. I’m a happy camper again. 😀

[Doug1016]

I ended up deleting the app and reinstalling it, and it worked fine after that.