Cannot setup Fitbit Versa on Android P

[codyl]

I bought this watch today and I'm not able to set it up with my phone. I recently updated my phone OTA (Pixel 2) using the Android P Beta Program.  I have a Charge 2 which works fine.

What happens is it gets to where I need to enter the pin shown on the watch and the app just kicks back into the Account Screen and the watch just has the Fitbit animation playing over and over.  A couple of times after putting in the pin my phone has said, "Fitbit has crashed".

I'd rather not have to downgrade my phone. So any help would be great. Thanks!

Update:  I just tried to re-add my Charge 2 and the same thing happens.  My Charge 2 was synced to my phone before I updated to Android P and was working fine while running Android P.  Now I can't add any device to my phone :(.

Update 2: I forgot to mention that my wife has the exact phone as me (Pixel 2) but she did not update to Android P.  She was able to sync her Versa without issue using Fitbit App version 2.71.  Since the same thing happens with both my old Charge 2 and my new Versa, I'm inclined to believe that the issue is definitely Android P.  Should I submit a support ticket with Fitbit so they more directly know about this issue?

[Matthew1471]

As Android P is the upgrade to Android 7, I suspect we may be linked : https://community.fitbit.com/t5/Android-App/Bug-Report-New-Android-App-2-71-Crashes-On-Android-7-mig...

---

@codyl wrote:
My Charge 2 was synced to my phone before I updated to Android P and was working fine while running Android P.  Now I can't add any device to my phone :(.

---

Fitbit App version 2.71 was released a few days ago when these problems started for me. I suspect your app updated via the Play Store too.

[GenieFish]

Do you guys have Windows 10 & Bluetooth?

My device is currently unsupported (Google Pixel 2 XL) and I found it was just so much less stressful to do things on the Windows 10 app. I know it's not ideal, but it may help. 

[Matthew1471]

---

@GenieFish wrote:

Do you guys have Windows 10 & Bluetooth?

---

Nope, I tried with Windows 8.1 but found out I don't have a Bluetooth 4.1 (Bluetooth LE) device which the fitbit Versa required.

As mine is already paired I just turn off all day sync and that keeps it stable (apart from for firmware updates). If I need to I can fall back on the NVidia Sheild tablet which seems to work better with this version.

[codyl]

---

@Matthew1471 wrote:

As Android P is the upgrade to Android 7, I suspect we may be linked : https://community.fitbit.com/t5/Android-App/Bug-Report-New-Android-App-2-71-Crashes-On-Android-7-mig...

That link does not work so I can't see if it's the same thing.

Some more information. My wife has the same phone (Pixel 2) as me but she did not update to Android P and she was able to attach the new versa to her phone. She has the same Fitbit App version as well (2.71). So the only difference is me updating (apparently stupidly) to Android P.

[codyl]

---

@GenieFish wrote:

Do you guys have Windows 10 & Bluetooth?

My device is currently unsupported (Google Pixel 2 XL) and I found it was just so much less stressful to do things on the Windows 10 app. I know it's not ideal, but it may help. 

---

I only have Linux and macOS. Fitbit does a macOS app, but it does not allow syncing of the Versa (and a couple others). You have to use your phone for the Versa.

[sam143569]

I started having same issue let me know if you find any solution

[Matthew1471]

---

@codyl wrote:

---

That link does not work so I can't see if it's the same thing.

---

Automatically flagged as spam for some reason, link should now be live.

Am thinking we might not be totally related though as it seems to be working on your wife's (unless they specifically play with the max jobs value in Pixel version Android P) and it works on another Android 7 device I have. So it must just be each manufacturer tweaks settings (such as max jobs) and I've hit that issue.

Did you manage to get a stack trace of your error? That would probably be the best indication of what's going on.

[SunsetRunner]

having the same issue here.  It will pair with Bluetooth but even after a successful completion of the wizard in the fitbit app, it won't appear as a device in the app.

[codyl]

---

Did you manage to get a stack trace of your error? That would probably be the best indication of what's going on.

---

I did not... Easiest way to get that? I'm a software engineer, but not a mobile developer.

[AlessFitbit]

@codyl Thanks for reporting this here on the Community! Our team is aware and investigating. We should have a fix in place in a future app version. I will confirm here when that happens.

[codyl]

---

@AlessFitbit wrote:

@codyl Thanks for reporting this here on the Community! Our team is aware and investigating. We should have a fix in place in a future app version. I will confirm here when that happens.

---

Thank you!! 🙂

[bsaurus]

Having the same issue. 

[Matthew1471]

---

@codyl wrote:

---

Did you manage to get a stack trace of your error? That would probably be the best indication of what's going on.

---

I did not... Easiest way to get that? I'm a software engineer, but not a mobile developer.

---

When you get a crash click "Send feedback" there will be a clickable link in the text of "account and system info" scroll down and there should be "Stack trace" with a down arrow.. that should tell you from top to bottom what caused the issue.. you can screenshot it.

However if you just click Send Feedback and send feedback then that all gets send to proper fitbit people. I am merely curious to see if it's the same issue as me out of sheer nosiness.

Mine starts "java.lang.IllegalStateException: Apps may not schedule more than 100 distinct jobs" and then goes further and further up the code chain.

[eidiotwind]

Same issues os OP. Running Android P beta on Pixel 2 XL.

[Devinm5]

I'm having the same issue. I was able to log in and set up my versa on another device, and then have it show up on my Pixel 2 XL with Android P (Beta) however i am experiencing major sync issues. has this been noted as an issue?

[FezzikTheGreat]

---

@GenieFish wrote:

Do you guys have Windows 10 & Bluetooth?

My device is currently unsupported (Google Pixel 2 XL) and I found it was just so much less stressful to do things on the Windows 10 app. I know it's not ideal, but it may help. 

---

I was about 5 minutes away from wiping my phone and reverting to Android Oreo 8.1 on my Pixel, syncing with the Win 10 app is, as you said, not ideal but it's a heck of a good solution for the time being.  Thanks!!

[RobertoME]

Hello there Android fellows, thank you for keep reporting this issue with Android P.

Note that this is the ninth version of the Android OS and still is in a beta version. So, in these scenarios is prone some issues with the Fitbit app and trackers may affect the functionality. Nonetheless, as it was mentioned before, our team is already aware of this issue and is under investigation.

Additionally to this, I want to inform you, there is a new version of the Fitbit app. That despite it doesn not have a direct fix for this issue, it contain some stability improvements. For more details, please refer to this post.

See you around and keep reporting any eventuality regarding this topic.

[AlessFitbit · Accepted solution]

Hi, everyone!

If you haven't already done so, please update to the latest version of the Fitbit for Android app version:2.72. This app version contains fixes for this app crash. 

Please let me know how it goes! If you're still seeing this happen after updating let me know. 

[codyl]

---

@AlessFitbit wrote:

Hi, everyone!

If you haven't already done so, please update to the latest version of the Fitbit for Android app version:2.72. This app version contains fixes for this app crash. 

Please let me know how it goes! If you're still seeing this happen after updating let me know. 

---

Awesome! I'll give it a go when I get home from work in about 4 hours.  I'll "Accept as Solution" if it works. Thanks!