"Updating database" hangs, can't access app

[Meregrotta]

the app updated to version 2.44 late last night and since then won't open, it hangs on trying to update the database.  I appear to be running iOS 11.1.2 and I'm one of the people for whom the app hasn't stayed logged in for more than a couple of hours at a time for months now.

I'm getting rather fed up.

Moderator edit: edited title for clarity

[SunsetRunner]

Hi

Does the issue occur when using Wifi or Mobile internet? (costs can apply when not having a data plan).

Feel free restarting the phone and turning off / on the internet router.

[Meregrotta]

Both under wifi and data.

[Meregrotta]

and rebooting my phone changed nothing.

[SunsetRunner]

Thank You

Feel free to check out the apple support page: If an app unexpectedly quits, stops responding, or won’t open

* Credit to Authors of the page.

Hope it helps

[Frad99]

App is locked on upgrading database screen 

keeps on saying retry but will not complete and syn

[ACG]

Hello @Frad99

This link has helped me complete the download. 

You need to "forget your device"

You will find the steps on here:

Why can't I update my tracker.
https://help.fitbit.com/articles/en_US/Help_article/2047

[adegroot1]

I have the same thing on my iphone 6. Untill beginning of the week it was fine, however it gives this message for a couple of days allready. 

And it has nothing to do with syncing to my watch I think as this is a database cleanup that is somehow not working correct.

[Ulrikadragen]

Since the last upgrade 13th dec, my app wont start. I get the errormessage ”Oops something sent sting. Try again” with one button Retry. It comes when the app says Updating the database. What is wrong?

[ErickFitbit · Accepted solution]

Have you all tried to uninstall and reinstall the app and giving it another try? If not, I recommend giving that a try and letting me know the results.

[Ulrikadragen]

Reinstalling the app helped. Thanks!

Ulrika Dragén

[littlepoint]

I reinstalled the app yesterday, and it worked all right. But today, the problem occurs again. Oops...

[KateFitbit]

@littlepoint - sorry to hear this, our team is working on a resolution. I'll update this thread as I hear more.