Health Connect not functioning (Android 14 - Quest Move)

[ThatGuyJacobee]

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. 🙂

[crany]

Thanks for keeping us updated and for trying to get this on the table.

But like everyone else already mentioned, it's a pretty poor "solution" that we now have to beg for it as a new idea. If Meta doesn't intend to fix it, at least make this clear in the app and update the FAQ and stuff. But probably it's easier (and much better for everyone involved), to just fix it.

Like the others mentioned, Health Connect is pretty well documented and I can't count how many otherwise **bleep**ty apps I've seen that updated for it a very long time ago.

[danthespaceshipman]

any chance you can chase this issue up, has been added back into ideas however not sure it should be raised there as this is not a request for new functionality but a request for meta to fix broken functionality  https://communityforums.atmeta.com/t5/Ideas/Meta-Quest-Move-support-for-syncing-data-to-Android-14-H...

[KaminasWife]

Hey there, I'll be filling in for the other mod! 

I'll bring this back up as we understand this is an issue for you all, but the ideas thread is still the best place for posting suggestions like this as this is, technically, intended behavior and not necessarily a software bug or the likes. 

Thanks for understanding!

[ladybones00]

Please explain how this feature NOT working is "intended behavour" 😆 

[KaminasWife]

The issues been flagged with our engineers. We appreciate your patience.

[LayerCakeMakes]

This whole ticket should not have been marked as solved, it's not solved.
Probably marked closed to fullfill some internal statistic. 

It's really no wonder the Android App has a rating of 2.5 Stars if issues are just avoided and silenced instead of being solved.
Again according to Google's own guides this should be mere hours of work to solve, and this has been this way for most of a year, most of the Quest 3's lifetime. Android 15 Source Code is already officially released, and it has not once worked in the whole lifecycle of Android 14.

[ThatGuyJacobee]

Agreed. It's ridiculous that we have been treated like this for so long. We purchased our headsets with the promise of MOVE integration with our phones as a feature... we have not been able to use this for over a year now, we technically have been misled by Meta here which is illegal. MOVE has not worked on anything above Android 14+ since the day it was released. Meta should have updated their SDK and app MONTHS in advance of Android 14. Google provided developers with information about this months in advance, yet Meta has not only failed this but failed the subsequent ENTIRE YEAR to do this. Disabling the feature is not a solution!!

But I'm sure Meta will continue to throw surveys at our faces on this forum and via the app... quite comical given that evidently they do not care about the feedback we have been providing for over a year now!!

This impacts ALL Android users that are on Android 14 and above (which at this rate would be a decent proportion)... how is this not considered a critically important issue. To reiterate, disabling the feature is not a solution, it's an insult to Android users who use Meta VR products. 🙄