04-18-2026
17:50
- last edited on
04-18-2026
22:47
by
ManuFitbit
04-18-2026
17:50
- last edited on
04-18-2026
22:47
by
ManuFitbit
I’m using Inspire3. The basic functions work fine and it syncs with my iPhone without issues, but there’s a bug in the iOS app.
After selecting the device, if I tap on a clock face or app button, it just gets stuck on the loading screen and freezes.
Has anyone else experienced the same problem?
I’ve already tried restarting the device, re-pairing it, restarting my iPhone, deleting and reinstalling the app, and turning Wi-Fi off/on — nothing has fixed it.
Moderator edit: clarified subject.
Community Moderators ensure that conversations are friendly, factual, and on-topic. We're here to answer questions, escalate bugs, and make sure your voice is heard by the larger Fitbit team. Learn more
Hi @Ryogo. Welcome to the forums.
I appreciate you taking the time to share your feedback regarding the Charge 6 and thank you for trying to fix it on your own.
I understand how frustrating these difficulties can be. This issue has been escalated and our team is actively identifying a fix.
Thanks for your patience while we resolve this. We look forward to having your device up and running again.
Keep an eye on the forums for any updates.
Best Answerhey, same issue here with iOS. tried fixing it the whole evening. glad I found this thread. Can you already say when to expect the fix or at least where I can find out when a fix has been released?
thanks!
I’m having the same problem & since I just got my first Fitbit 3 days ago I have been going crazy trying everything I can think of (sign out, delete app, restart phone, reinstall app, etc.) to get it to work and still just get a blank white screen with a spinning circle on it whenever I click on “Change Clock Face” or “Apps”. Hope it’s fixed soon so I can actually use all the great features of my new device!
Having the same issue - my clock face is buggy but the screen won’t load so I can change it. I’ve tried everything suggested in this and other threads with no luck. When will this be fixed???