-
-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Device info doesnt return device model #163
Comments
Hey! Can you debug the app with Android Studio and add a breakpoint here? Then check what's in the Lines 26 to 33 in d7faf11
If the recording method is the same as you see in the javascript side, there is nothing I can help you with. |
@matinzd Yes recording method is the same. Does it mean that this problem is not in the library, but in Google Fit or Health Connect itself ? |
How about other information like device metadata? Yes, then the problem is not with the react native lib. You need to open an issue in Google Issue Tracker. |
@matinzd All the data is same. I get it, thanks a lot for you responses. I will open an issue in Google Issue Tracker |
@matinzd I am super sorry for bothering you, but have you seen latest changes of |
@nikitabalabanovdev What do you mean? |
@matinzd
### Device metadata always returns null values in Health Connect library
Description:
When fetching activity data, the metadata?.device object consistently returns {"manufacturer": null, "model": null, "type": 0}. This behavior occurs regardless of whether the code is running on an emulator or a real device. The expectation is that the manufacturer and model fields should return the device information for real devices and appropriate metadata for emulators.
Steps to reproduce the behavior:
Expected behavior:
The metadata?.device should return the actual device details
Minimal Reproducible
Here’s a code snippet demonstrating the issue:
Environment:
Health Connect Version: ^3.1.0
React Native Version: 0.72.7
New architecture enabled: No
Using Expo: No
Android API Level: API 34 (Android 14)
The text was updated successfully, but these errors were encountered: