DeepQuail4 weeks ago
This issue occurs when your app requests Health Connect permissions that don't match what was approved by Google for production use, or when there are duplicate permission entries in your AndroidManifest.xml.
Common Causes:
Resolution Steps:
<uses-permission android:name="android.permission.health.READ_BASAL_METABOLIC_RATE" tools:node="remove"/> <uses-permission android:name="android.permission.health.READ_BODY_WATER_MASS" tools:node="remove"/> <uses-permission android:name="android.permission.health.READ_BONE_MASS" tools:node="remove"/> <uses-permission android:name="android.permission.health.READ_EXERCISE" tools:node="remove"/> <uses-permission android:name="android.permission.health.READ_HEIGHT" tools:node="remove"/> <uses-permission android:name="android.permission.health.READ_MENSTRUATION" tools:node="remove"/> <uses-permission android:name="android.permission.health.READ_POWER" tools:node="remove"/> <uses-permission android:name="android.permission.health.READ_SPEED" tools:node="remove"/> <uses-permission android:name="android.permission.health.READ_WEIGHT" tools:node="remove"/>
Remove duplicate permission entries - ensure each permission appears only once in your AndroidManifest.xml
Remove duplicate meta-data tags - ensure you have only one instance of:
<meta-data android:name="health_permissions" android:resource="@array/health_permissions"/>
Note: This issue may be more prominent on certain devices (like Samsung Galaxy Fold series) due to device-specific Health Connect implementations.
For complete Health Connect setup instructions, see the React Native documentation.
StaticPython2 weeks ago
Only check
Cookie Preferences