Android Beta 3.56.1 - "Nearby Permission Needed" but no such permission in settings

[R_G_B]

After update today to Fitbit Android Beta app 3.56.1 when I open the App it says that Nearby Permission is needed.  Takes me to setting but in Android setting I have no Nearby Permission.  I have given Fitbit All permissions but still get the error message in the app.

Android 12, Fitbit Sense, Beta App 3.56.1, Samsung Galaxy Note 20 Ultra

Moderator edit: Subject for clarity.

[Brendan6982]

The 3.57 version just came out.  Nearby permission issue still exists.

 

[MrGlenn]

Issue persists in beta 3.57. Permissions still not implemented properly.

I would laugh, if it wasn't so [edit: forum censors naughty words] infuriating.

It's not even like this was an emergency fix a few days later. They clearly went through their entire sprint, finalized a new release and uploaded it to their store.

And they still missed this issue completely..?

Congratulations team, I was trying to point people to where they should be leaving their feedback but apparently you DON'T take that into consideration...

[psmith711]

Thank you so much!  I thought I had a problem with my sense and was told since it was out of warranty there was nothing they could do.  I bought a new one and had the same problem.  Finally see your post and now it is working great

Chatted several times with the Fitbit people and they never mentioned this fix to me.  Said they would escalate the problem and get back to me and they never did

[Rich_Laue]

Your beta has its own Google discussion group, you might want to discusgtgisgwith the users that are testing the beta version. 

[Lilbiddy]

@Rich_Laue  on page one @R_G_B says Google Groups has gone away.

[MrGlenn]

Spoke with a customer service rep today, and asked him to escalate this issue if it hasn't already been done so. Sure we can roll back to the non-Beta release, but public Beta's exist for a reason so feedback like this should be monitored closely.

Shared this thread with them also and they said they would make sure it would reach the appropriate team.

Let's hope it does, or at least that there is some official acknowledgement here at least.

[Rich_Laue]

And as beta users, we understand that things may not go smoothly 

[R_G_B]

@Rich_Laue  Yes, things may not go smoothly but as beta users, we also expect somewhere to report the issues and have developers respond to what's going on.

The beta group on Google Groups went away when Google shut down Google Groups a couple of years ago.  Since the there is nowhere to report issues other than the Play Store to which there has been no response from anyone.  This has been going on for about two weeks now and Fitbit devices are not able to sync without this permission.

Posting here has so far gotten the response that "Betas should not be discussed in public", "it has been forwarded to the correct department" and "I'm sure it will be fixed soon".  Other users have reported that they talked to support and that the issue would be elevated.  I would think that as a developer, any issue that prevents users from syncing their device would receive top priority.  At least that could ask for more information if needed.  Imagine releasing a beta with a known issue like that for general deployment.

Fitbit just doesn't seem to even want to say "Hey we are aware of the issue and working on it.

And just as a note, it is a PUBLIC beta so anyone can join.  

[JRC6305]

So I'm having the same issue now for 2 weeks.  After my first call a week ago, they told me since my Versa 3 was out of warranty I needed a new one.  It was nice of them to send me a “coupon code” would have been nicer if it worked off on top of the already discounted price, but it only worked off the “original” price. 😤 Just got the new Versa 3 today and guess what same issue!  Spent an hour on the phone with them and pointed them to this and another similar thread, which they appreciated, but had “no idea” there was this issue.  Also told them I was in the beta version and asked them if there was a way to get RID of the beta version of the App - he said no 😠.  They have “escalated” it to a higher group. . . but I don’t suspect I’ll hear from them anytime soon – at least based on all the posts here.  But thanks to all of you I am now trying the option of having “left” the Google Play beta group.  Just waiting for it to complete and will try again with my original watch, cause if it works, I’m returning the new one!!! 

IT WORKED!!!!  

I called the "help desk" back and told them how it gets fixed (thanks to all of you 😀) and that the poor guy that answered this time got an earful, but he added it to my Case# and . . . I got a free return label to return the new watch cause my old one works just fine thank you!!!

[MrGlenn]

Another 2 week sprint, another beta version update: 3.58.

Nothing resolved, still the exact same critical issue. 

@RodrigoFitbit what exactly are your developers 'testing' on these beta versions? How can you test something where the core functionality is missing?

Please clarify if we should just never participate in the beta channel anymore. Do you not want regular users to contribute to it..?

At this point, just pull the beta channel from the Play store altogether, that might make Fitbit look more professional...

[LokeAa]

I don't get why participants in the Beta programme are surprised not all features / functions don't work as expected. A beta version is NOT a stable version, if it was, it would not be a beta. Just sayin'.

[Brendan6982]

It will not sync or due anything. It is now just a dumb watch.

[LarrySernyk]

You should consider leaving the beta program. After you are out of the beta you will need to uninstall and reinstall the public version. I did this and working fine now.


⁣Get BlueMail for Android ​

[scuttlefield]

While your point about beta programs is correct in general, typically you don't roll out multiple update of your beta with a well-documented critical bug. I fully expect bugs like this to happen. It's the devs' (non) reaction to the critical bug that's unexpected.

This is especially true of a public beta where you're wanting user to test your beta builds. This will just make everyone leave the beta and have no idea when to come back to it.

[LarrySernyk]

I agree with your comments. We had had issues in the past with Beta versions but Fitbit had responded to correct them. There was a gmail group that we would report issues to Fitbit but that no longer works and you cannot contact the app owner through Google Play store. I enjoyed being part of the Beta in it's early years because I liked to get a look at new features and test them.

I still continue to participate in the beta testing for my Fitbit Sense device when I am accepted. My Fitbit Sense now does Core Dumps when there are issues which I believe may be Google's way of collecting data and correcting issues. You can sign up for that beta if you are not already a beta tester for your device. I am looking forward to some cool new features in a Sense 2 which I hear is in the works.

[leakejl]

how do you uninstall the beta version?  If I uninstall the app the only option I see to reinstall is the beta version.  

[jsykes]

Go to the app in Google play and scroll down until you see the option to leave the beta. Uninstall the app, and give it a few minutes or so, then you should see the regular Fitbit app to install. It took about 5 minutes for the beta to clear. 

[scuttlefield]

Had a thought that maybe the current Fitbit beta had been designed for Android 13. Since the first Android 13 beta was released yesterday, I installed it and then re-joined the Fitbit beta. I was so hopeful, but it STILL didn't work. All I can think is the the Fitbit beta has been designed for something that will be added in Android 13... or it's some compatibility thing related to the Pixel Watch that's supposed to be unveiled in May. Either way, if that's the case, the Fitbit Beta should have been moved to a private beta.

[RodrigoMFitbit]

Hello everybody. Thanks for sharing your experience with the beta version of the Fitbit app. 

I was advised that you should provide all feedback regarding the beta Fitbit over the the sign in at https://beta.fitbit.com/. I have forwarded your comments but all feedback should go through this website. Thanks for sharing your experience with the beta programm.

Have a nice day!

[scuttlefield]

Thank you. That's helpful.

Hey RodrigoMFitbit

Just FYI, I went over to https://beta.fitbit.com/ ... I didn't realize it was a full-on device testing program (Fitbit Field Testing), where you have to give tons of information. I'm not really interested in doing all that right now, just testing the public beta app. So, I guess there's really no way to provide feedback without fully signing up for Fitbit Field Testing?