Participant

Question

Health Connect not functioning (Android 14 - Quest Move)

74 replies
25763 views

Beginning Android 14, Google is moving their Health Connect Google Play app into a native system built-in app. This has caused the Meta Quest app to stop being able to sync data to Health Connect. Most other health apps have already had updates to adjust for this change, but the Meta Quest app still hasn't received an update to solve this.

I'm running the One UI 6 Beta 2 (Android 14) and I cannot get Health Connect set up with the Oculus app because I receive a message stating that the Meta Quest app must be updated to continue integrating with Health Connect.

Hope you can solve this ASAP as I want to sync my Quest Move data again. 🙂

verglor

New Participant

I have the same problem ☹️. Unfortunately Google broken sync with all apps that didn't update to new Health Connect. But the problem is here since August so I think it's about time to update Meta Quest app already.

ThatGuyJacobeeAuthor

Participant

Yeah, I'm sure Meta has had plenty of early information about this from Google as a play store developer, so it is a shame to see them take this long to implement this. I can assume it is a very simple change in the app too, nothing big but it has taken so long and who knows how much longer. Perhaps they were busy prioritising Quest 3 support etc. over the past few weeks/months but regardless I hope a mod or some dev can see this post to prioritise this. 👍

O

OpusOculusAccount

New Participant

Have had the exact same issue since the move to Android 14.

LayerCakeMakes

Participant

My phone also updated itself to 14 and now it's broken.

BlueberrieSmoothie

Honored Contributor

Hi! 👋 Friendly neighborhood mod chiming in to say I did see this! Thank you so much for bringing this to the Forums. Being able to connect your health app is such a great feature for Quest, and I want to make sure that we can find a way to get this working with Android 14 as well.

For some more visibility, I just brought this to our engineers so they can take a closer look at what's going on. Since they always need some specific details, if you all could, please provide the following:

Type of phone you are using
Software Version of your Meta Quest mobile app
Software version of your headset

I'll continue to keep this thread updated with any news I hear back! For now however, since this is being looked into, I will be marking my response as the solution so that anyone who sees this post can easily see the current status as well as what information the engineers need from those affected.

EDIT 12/8/23 - Hey everyone! I wanted to jump in and let y'all know that I still haven't heard from the engineers on this quite yet, but I am continuing to check with them to make sure this gets addressed.

EDIT 1/3/24 - I got an update, and wanted to make sure I shared the info I got with all of you. Per our teams, this feature is currently disabled until Move updates its API for Android 14. At this point, they're waiting on Google for this.

EDIT 1/18/24 - After checking in with the engineering team on this again, they informed me that this feature has been disabled. I know this isn't the ideal outcome. I would strongly urge anyone who wants this feature back to post about it on the Ideas section of the Forum. That is the best way for this to gain traction and get seen by the teams who can affect change like this.

Make sure you smash that Kudos button!

verglor

New Participant

Hi BlueberrieSmoothie, thank you for taking care of this issue...

My specific details:

Type of phone you are using: Pixel 6a (Andorid 14 QPR Beta U1B2.230922.010)
Software Version of your Meta Quest mobile app: 233.5.1.18.115
Software version of your headset: Quest 2 v57

L

ladybones00

Participant

I am confused. How do wex'' proceed here? Is there another way to get the move info out of the headset? It's completely useless otherwise

LayerCakeMakes

Participant

Phone: Pixel 7 Pro
Android Version: 14 (UP1A.231005.007)
Meta App: 233.5.1.18.115
Headset: Meta Quest 3 on Current Version

This is purely an App issue on Android. All the things that need to be updated can be found in this Android Developer announcement: https://developer.android.com/health-and-fitness/guides/health-connect/migrate/migrate-from-android-13-to-14

LayerCakeMakes

Participant

Question to the people affected by this, do you also have the issue on the phone app when you look at the Meta Move month view (click calendar button in the day view) that all the tracked days are dated 6 days into the future?

I already have a checkmark for goal achieved up to the 28th in the month view and today is the 22nd...

ThatGuyJacobeeAuthor

Participant

Yeah, I have also noticed some weird inconsistencies with the monthly calendar preview. For example, on October 15th I done my weekly goal and all the max targets, but on the calendar it displays as empty. When I click onto it though and open the date up, it shows fine in there. I've had this happen on a couple of days. Likewise, on October 22nd, preview states I did workout but opening up it shows that I didn't (which is true didn't use VR that day).

Very weird behavior, I assume something to do with this issue probably and like you said, it's dating the previews incorrectly or at a weird index/offset.

LayerCakeMakes

Participant

BlueberrieSmoothie should we create another post for the month view issue or can you just communicate that to the devs as another issue with Meta Quest Move sync on Android.

BlueberrieSmoothie

Honored Contributor

If this started around the same time, I figure this is likely related to something with the integration now that the Android app has changed. Hopefully if the connection/integration part of this get fixed, this will get resolved along with it!

Make sure you smash that Kudos button!