08-15-2025
05:47
- last edited on
08-20-2025
12:12
by
AndreaFitbit
08-15-2025
05:47
- last edited on
08-20-2025
12:12
by
AndreaFitbit
Why won’t my Fitbit connect thru power sync anymore to apple health anymore. Have not had this issue before.
Moderator Edit: Formatting.
08-15-2025 11:38
Platinum Fitbit Product Experts share support knowledge on the forums and advocate for the betterment of Fitbit products and services. Learn more
08-15-2025 11:38
Hello @Jaxman7
I moved your post from the Charge 6 product help forum to the iOS platform forum where you are more likely to get help from other iOS users.
Rieko | N California USA MBG PE
Best Answer08-15-2025 12:15
08-15-2025 12:15
Having the same problem, stopped syncing on August 12, 2025. I wonder if its the new Google/Fit bit account blocking access.
08-15-2025
15:28
- last edited on
08-20-2025
11:34
by
AndreaFitbit
08-15-2025
15:28
- last edited on
08-20-2025
11:34
by
AndreaFitbit
Might be. Mine quit the same day!
---
Thank you
08-16-2025 22:32
08-16-2025 22:32
I am also having issues with PowerSynv on my iPhone (latest iOS update), latest version of FitBit and PowerSync - mine is crashing each time I run is and then annually sync. Am not sure if automatically sync is working or not. I am also when I try Sync Solver (but with that one I can partially sync. - see attachment for error message).
08-17-2025 00:20
08-17-2025 00:20
’m experiencing the same issues. I’ve tried every solution possible, but nothing seems to be working.
08-18-2025 18:56
08-18-2025 18:56
I’m having the same issue also
08-18-2025 21:50
08-19-2025 22:01
08-19-2025 22:01
Is yours working now?
08-20-2025 02:49
08-20-2025 02:49
As of this morning the issue still remains. Thank you for asking.
08-20-2025 02:57
08-21-2025 08:37
08-21-2025 08:37
Same, How does fitbit not have a native app built to sync with Apple?
08-24-2025
19:13
- last edited on
08-27-2025
09:31
by
AndreaFitbit
08-24-2025
19:13
- last edited on
08-27-2025
09:31
by
AndreaFitbit
I am having this same issue and have done all the suggested fixes too. Nothing works. Mine also stopped syncing around 8/12
Moderator Edit: Formatting.
08-26-2025 05:00
08-26-2025 05:00
Same. Mine stopped working 8/12
Best Answer08-26-2025 17:14
08-26-2025 17:14
Same here. Stopped syncing on August 12th.
Best Answer08-29-2025 20:41
08-29-2025 20:41
Same here stopped working, Is there any solution
Best Answer08-30-2025 01:27
08-30-2025 01:27
Interesting thing is that I have been able to sync for the last day or so via Sync Solver to Apple Health but I still can’t via Power Sync. I have confirmed there has not been an update on sync Solver and I have confirmed I am running the latest FitBit app (version 4.50)
Best Answer08-30-2025 04:42
Diamond Fitbit Product Experts share support knowledge on the forums and advocate for the betterment of Fitbit products and services. Learn more
08-30-2025 04:42
Hi @LFWJR Fitbit and Apple have always been competitors in the smartwatch market. That competitive distinction got bigger when Google bought Fitbit.
Laurie | Maryland
Sense 2, Luxe, Aria 2 | iOS | Mac OS
Take a look at the Fitbit help site for further assistance and information.
Best Answer09-01-2025 02:17
09-01-2025 02:17
Am having same problem, no reply when you email them, am going to start looking for an alternative when paid subscription is up shortly
Best Answer09-02-2025 23:22
09-02-2025 23:22
I noticed the same problem. Power Sync crashed every time I tried to sync, and the last successful sync was recorded as being on 8/4/24. I looked at the Apple App store and noticed that the last update to Power Sync was 4 years ago, so I guess the developer has dropped it.
I just installed "Auto Sync with Fitbit" from MPR Media Inc. I chose it because it seems to be actively supported by its developers (recent updates) and it has decent reviews. It appears as "SyncFit" on my iPhone and it came with a 3-day free trial before it automatically converts to a $39.99/yr annual subscription. I was able to set it up without any issues and it seemed to successfully sync my data with Apple Health, so I'm going to cautiously call this a fix.