-
Notifications
You must be signed in to change notification settings - Fork 134
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
Address new ACTIVITY_RECOGNITION Android permission #178
Comments
looks like something new introduce by Android 10. The permission is automatically granted if you target Android 9 or lower, which may fix it temporarily. For future implementations, it would be better to include this when requesting permissions for these specific data sets. Very happy to receive PRs in this regard. |
@dariosalvi78 yes it works for me, thanks! For 10 android need to do the following:step 1: add plugin android permissions
step 2: go to the config.xml file in the root folder and add:
step 3: request permissions ACTIVITY_RECOGNITION and then perform the necessary actions...
|
I want to keep this open as the solution should be included in the plugin. |
Great plugin! Has the problem with steps regarding the Android 10 permission been solved? |
I've been going through this: the current cordova android support targets API version up to 28 (Android 9). This makes it impossible to use the new permissions on a regular cordova project. How did you get into this problem? |
You can find the relevant info here: https://cordova.apache.org/announcements/2020/06/29/cordova-android-9.0.0.html
Google forces 29 as the minimum target API.
…________________________________
From: Dario Salvi <[email protected]>
Sent: Tuesday, October 13, 2020 12:18:48 PM
To: dariosalvi78/cordova-plugin-health <[email protected]>
Cc: Göktuğ Aşcı <[email protected]>; Comment <[email protected]>
Subject: Re: [dariosalvi78/cordova-plugin-health] Address new ACTIVITY_RECOGNITION Android permission (#178)
I've been going through this: the current cordova android support <https://cordova.apache.org/docs/en/latest/guide/platforms/android/> targets API version up to 28 (Android 9). This makes it impossible to use the new permissions on a regular cordova project. How did you get into this problem?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#178 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AHBDRJKCHHINFAL6YFE3TGTSKQSQRANCNFSM4N6CVLZA>.
|
preference name="android-targetSdkVersion" value="29"
…________________________________
From: Göktuğ Aşcı <[email protected]>
Sent: Tuesday, October 13, 2020 12:35:30 PM
To: dariosalvi78/cordova-plugin-health <[email protected]>; dariosalvi78/cordova-plugin-health <[email protected]>
Cc: Comment <[email protected]>
Subject: Re: [dariosalvi78/cordova-plugin-health] Address new ACTIVITY_RECOGNITION Android permission (#178)
You can find the relevant info here: https://cordova.apache.org/announcements/2020/06/29/cordova-android-9.0.0.html
Google forces 29 as the minimum target API.
________________________________
From: Dario Salvi <[email protected]>
Sent: Tuesday, October 13, 2020 12:18:48 PM
To: dariosalvi78/cordova-plugin-health <[email protected]>
Cc: Göktuğ Aşcı <[email protected]>; Comment <[email protected]>
Subject: Re: [dariosalvi78/cordova-plugin-health] Address new ACTIVITY_RECOGNITION Android permission (#178)
I've been going through this: the current cordova android support <https://cordova.apache.org/docs/en/latest/guide/platforms/android/> targets API version up to 28 (Android 9). This makes it impossible to use the new permissions on a regular cordova project. How did you get into this problem?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#178 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AHBDRJKCHHINFAL6YFE3TGTSKQSQRANCNFSM4N6CVLZA>.
|
GH-848<apache/cordova-android#848> breaking: increased default target sdk to 29 this is an update of cordova-android 9.0.0
…________________________________
From: Dario Salvi <[email protected]>
Sent: Tuesday, October 13, 2020 12:18:48 PM
To: dariosalvi78/cordova-plugin-health <[email protected]>
Cc: Göktuğ Aşcı <[email protected]>; Comment <[email protected]>
Subject: Re: [dariosalvi78/cordova-plugin-health] Address new ACTIVITY_RECOGNITION Android permission (#178)
I've been going through this: the current cordova android support <https://cordova.apache.org/docs/en/latest/guide/platforms/android/> targets API version up to 28 (Android 9). This makes it impossible to use the new permissions on a regular cordova project. How did you get into this problem?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#178 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AHBDRJKCHHINFAL6YFE3TGTSKQSQRANCNFSM4N6CVLZA>.
|
this should be solved now. I haven't tested this thoroughly, so, before releasing a new version, I would appreciate a confirmation that this is working in your app(s). Please be aware that I have removed DOB and gender from Fit (didn't make sense) and that you will need to activate AndroidX if you use the latest Android platform (see README for that). |
How do we install it without being released with your latest commit?
…________________________________
From: Dario Salvi <[email protected]>
Sent: Thursday, October 15, 2020 4:11:15 PM
To: dariosalvi78/cordova-plugin-health <[email protected]>
Cc: Göktuğ Aşcı <[email protected]>; Comment <[email protected]>
Subject: Re: [dariosalvi78/cordova-plugin-health] Address new ACTIVITY_RECOGNITION Android permission (#178)
Closed #178<#178>.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#178 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AHBDRJIHL5N7T6QTZKNWDHLSK37IHANCNFSM4N6CVLZA>.
|
Physical activity permission works but body sensor permission is still missing.
…________________________________
From: Dario Salvi <[email protected]>
Sent: Thursday, October 15, 2020 6:19:26 PM
To: dariosalvi78/cordova-plugin-health <[email protected]>
Cc: Göktuğ Aşcı <[email protected]>; Comment <[email protected]>
Subject: Re: [dariosalvi78/cordova-plugin-health] Address new ACTIVITY_RECOGNITION Android permission (#178)
https://stackoverflow.com/questions/25140383/adding-plugins-from-specific-revision-github-project-to-the-cordova-project
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#178 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AHBDRJNPM5ZGPEJSUBRDZ3TSK4OI5ANCNFSM4N6CVLZA>.
|
what data type are you trying to access concretely? |
["distance", "calories", "steps"] this is my array.
…________________________________
From: Dario Salvi <[email protected]>
Sent: Thursday, October 15, 2020 9:34:09 PM
To: dariosalvi78/cordova-plugin-health <[email protected]>
Cc: Göktuğ Aşcı <[email protected]>; Comment <[email protected]>
Subject: Re: [dariosalvi78/cordova-plugin-health] Address new ACTIVITY_RECOGNITION Android permission (#178)
what data type are you trying to access concretely?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#178 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AHBDRJN2E2MUAKFQHSBIZCDSK5FDDANCNFSM4N6CVLZA>.
|
I have tested distance, calories and steps independently and they are working on my phone. I have found a little bug anyway so I recommend you pull the latest version and try again. |
There was a problem that on some devices we can't receive data from Google Fit. For example, in Xiaomi Mi 8, android 10, we always get the error
com.google.step_count.delta requires android.permission.activity_recognition
. All stages of authorization have been completed and permissions have been given everywhere to receive data:['steps', 'weight', 'blood_pressure', 'heart_rate']
. Inconfig.xml
are written:HEALTH_READ_PERMISSION
,HEALTH_WRITE_PERMISSION
But this error is rarely shown, and on many devices, after authorization, we can correctly get the data.
Has anyone encountered this problem?
The text was updated successfully, but these errors were encountered: