Missing permissions on targetSdk 33 #212

dharmraj2018 · 2024-01-08T09:54:40Z

FATAL EXCEPTION: main
Process: com.example.exercise, PID: 13281
java.lang.SecurityException: Missing permissions
at androidx.health.services.client.impl.internal.StatusCallback.onFailure(StatusCallback.kt:43)
at androidx.health.services.client.impl.internal.IStatusCallback$Stub.onTransact(IStatusCallback.java:74)
at android.os.Binder.execTransactInternal(Binder.java:1285)
at android.os.Binder.execTransact(Binder.java:1244)
Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [StandaloneCoroutine{Cancelling}@d760ae4, Dispatchers.Main.immediate]

yschimke · 2024-01-08T10:07:01Z

I think I know how it's happening, but could you add some text to explain how to reproduce apart from the stacktrace.

dharmraj2018 · 2024-01-08T10:23:51Z

I have run this demo on a Samsung Watch 5, (Android OS version 13, and Wear OS version 4.0)
and give all permissions after that just click on to Start button

yschimke · 2024-01-08T11:43:11Z

OK, it's working on emulator if you grant all permissions. But does fail if you deny.

So looks like a different issue than I guessed.

dharmraj2018 · 2024-01-08T12:09:51Z

Please see the video...
I have given all permission but not working on actual watch

PXL_2.mp4

ithinkihaveacat · 2024-01-08T12:40:27Z

@dharmraj2018 Thanks for the video. I can't reproduce on Pixel Watch 2 or the API 33 emulator. I don't have access to GW4 at the moment. Can you share your Health Services version?

$ adb shell dumpsys package com.google.android.wearable.healthservices | grep versionCode
    versionCode=1443860 minSdk=30 targetSdk=33
    versionCode=1405199 minSdk=30 targetSdk=33

dharmraj2018 · 2024-01-08T13:40:09Z

Hi @ithinkihaveacat please check the version. let me know if anything needs to upgrade version.
versionCode=1388651 minSdk=30 targetSdk=33

yschimke · 2024-01-08T16:15:54Z

@ithinkihaveacat I think there are multiple parts here

Why it's failing on GW
Catching the failure and showing an error
detecting/explaining which permissions are needed proactively

ithinkihaveacat · 2024-01-09T00:53:35Z

I'm having trouble reproducing the behavior shown in the video at #212 (comment).

Things I tried:

with com.google.android.wearable.healthservices versionCode 1388651 as in the original report (FWIW this is the version that comes with the OS and is pretty old, not sure why it hasn't updated but that's a separate issue)
with com.google.android.wearable.healthservices versionCode 1434827 (latest production)
with the device's global location setting turned off

yschimke · 2024-01-09T16:51:41Z

Linking here the docs for which permissions are needed - https://developer.android.com/health-and-fitness/guides/health-services/permissions

dharmraj2018 · 2024-01-12T04:55:16Z

Hi @yschimke @ithinkihaveacat do you have any updates for me?

ithinkihaveacat · 2024-01-12T14:30:14Z

@dharmraj2018 I'm struggling to reproduce this :-(. Tried another GW device just now and it works just fine. (Granting all permissions for now, as in #212 (comment).) It also works on the emulator. Can you reproduce on a different device?

dharmraj2018 · 2024-01-15T11:51:14Z

Hi @ithinkihaveacat , I have been able to run the app on the simulator successfully. However, I'm encountering issues when trying to run it on actual Samsung Watch 4 and 5 devices with the latest software version. Previously, it was working fine, but after updating the watch to One UI 5.0 (System version: 13 and Wear OS version 4.0), the app is not functioning properly, and I'm experiencing the same crash. Please assist in resolving this issue.

amankhoza · 2024-01-26T09:57:44Z

@dharmraj2018 can you post the results of this command:

adb shell dumpsys package com.example.exercise | grep -i -C10 "permissions"

Double check that the package is actually com.example.exercise, change it if its different.

amankhoza · 2024-01-26T11:07:06Z

@dharmraj2018 I think this should solve your issue #223, looks like the exercise sample was missing the POST_NOTIFICATION permission, you only need to request this on Wear 4, which explains why you only say this after updating, see: https://developer.android.com/training/wearables/versions/4/changes#notification-permission

yschimke · 2024-01-26T11:29:37Z

I'm unclear how this manifest as

java.lang.SecurityException: Missing permissions
at androidx.health.services.client.impl.internal.StatusCallback.onFailure(StatusCallback.kt:43)

If really required, we should add to https://developer.android.com/health-and-fitness/guides/health-services/permissions

dharmraj2018 · 2024-01-30T04:51:18Z

Hi @amankhoza
please check the results of this given command:

$ adb shell dumpsys package com.example.exercise | grep -i -C10 "permissions"
          Action: "androidx.work.impl.background.systemalarm.UpdateProxies"

Service Resolver Table:
  Non-Data Actions:
      hs.versionclient.BIND:
        4d29d7e com.example.exercise/androidx.health.services.client.VersionApiService filter 71da2df permission com.google.android.wearable.healthservices.permission.PASSIVE_DATA_BINDING
          Action: "hs.versionclient.BIND"

Domain verification status:

Permissions:
  Permission [com.example.exercise.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION] (3e988d):
    sourcePackage=com.example.exercise
    uid=10040 gids=[] type=0 prot=signature
    perm=PermissionInfo{b7fa1cb com.example.exercise.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION}

Registered ContentProviders:
  com.example.exercise/androidx.startup.InitializationProvider:
    Provider{6a5eda8 com.example.exercise/androidx.startup.InitializationProvider}

ContentProvider Authorities:
--
--
      com.google.android.wearable
    usesOptionalLibraries:
      androidx.window.extensions
      androidx.window.sidecar
    usesLibraryFiles:
      /system/framework/com.google.android.wearable.jar
    timeStamp=2024-01-15 17:11:36
    lastUpdateTime=2024-01-15 17:11:36
    packageSource=0
    signatures=PackageSignatures{a403c54 version:2, signatures:[fce376d4], past signatures:[]}
    installPermissionsFixed=true
    pkgFlags=[ TEST_ONLY ]
--
    pkgFlags=[ TEST_ONLY ]
    declared permissions:
      com.example.exercise.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION: prot=signature, INSTALLED
--
      com.example.exercise.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION: prot=signature, INSTALLED
    requested permissions:
      android.permission.BODY_SENSORS
      android.permission.ACCESS_FINE_LOCATION
      android.permission.ACTIVITY_RECOGNITION
      android.permission.WAKE_LOCK
      android.permission.FOREGROUND_SERVICE
      android.permission.ACCESS_NETWORK_STATE
      android.permission.RECEIVE_BOOT_COMPLETED
      com.example.exercise.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION
      android.permission.ACCESS_COARSE_LOCATION
--
      android.permission.BODY_SENSORS
      android.permission.ACCESS_FINE_LOCATION
      android.permission.ACTIVITY_RECOGNITION
      android.permission.WAKE_LOCK
      android.permission.FOREGROUND_SERVICE
      android.permission.ACCESS_NETWORK_STATE
      android.permission.RECEIVE_BOOT_COMPLETED
      com.example.exercise.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION
      android.permission.ACCESS_COARSE_LOCATION
    install permissions:
      android.permission.FOREGROUND_SERVICE: granted=true
      android.permission.RECEIVE_BOOT_COMPLETED: granted=true
      android.permission.ACCESS_NETWORK_STATE: granted=true
      com.example.exercise.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION: granted=true
      android.permission.WAKE_LOCK: granted=true
    User 0: ceDataInode=17960 installed=true hidden=false suspended=false distractionFlags=0 stopped=false notLaunched=false enabled=0 instant=false virtual=false
      installReason=0
      firstInstallTime=2024-01-15 17:11:36
      uninstallReason=0
--
      android.permission.FOREGROUND_SERVICE: granted=true
      android.permission.RECEIVE_BOOT_COMPLETED: granted=true
      android.permission.ACCESS_NETWORK_STATE: granted=true
      com.example.exercise.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION: granted=true
      android.permission.WAKE_LOCK: granted=true
    User 0: ceDataInode=17960 installed=true hidden=false suspended=false distractionFlags=0 stopped=false notLaunched=false enabled=0 instant=false virtual=false
      installReason=0
      firstInstallTime=2024-01-15 17:11:36
      uninstallReason=0
      runtime permissions:
        android.permission.ACCESS_FINE_LOCATION: granted=true, flags=[ USER_SET|USER_SENSITIVE_WHEN_GRANTED|USER_SENSITIVE_WHEN_DENIED|524288]
        android.permission.BODY_SENSORS: granted=true, flags=[ USER_SET|USER_SENSITIVE_WHEN_GRANTED|USER_SENSITIVE_WHEN_DENIED]
        android.permission.ACCESS_COARSE_LOCATION: granted=true, flags=[ USER_SET|REVOKE_WHEN_REQUESTED|USER_SENSITIVE_WHEN_GRANTED|USER_SENSITIVE_WHEN_DENIED]
        android.permission.ACTIVITY_RECOGNITION: granted=true, flags=[ USER_SET|USER_SENSITIVE_WHEN_GRANTED|USER_SENSITIVE_WHEN_DENIED]
      enabledComponents:
        androidx.work.impl.background.systemjob.SystemJobService

Queries:
  system apps queryable: false
  queries via forceQueryable:

yschimke · 2024-01-30T08:55:30Z

Is our sample missing BODY_SENSORS_BACKGROUND ?

Also discussed #101 and #190

amankhoza · 2024-01-30T14:22:30Z

@dharmraj2018 I was going to suggest the same as @yschimke, looking at the permissions you've mentioned in #212 (comment) the only one missing from https://developer.android.com/health-and-fitness/guides/health-services/permissions is BODY_SENSORS_BACKGROUND. This should only be necessary if you're using a PassiveMonitoring client or want to collect sensor data in the background, but regardless, try adding it to the REQUIRED_PERMISSIONS array in app/src/main/java/com/example/exercise/PrepareFragment.kt, and let's see if that works.

dharmraj2018 · 2024-01-31T04:34:27Z

Hi @amankhoza I already checked with having permission for BODY_SENSORS_BACKGROUND still crashing the same issue although Google Pixel Watch 2 is working fine without this permission. The problem is only with the Samsung watch One UI 5.0

amankhoza · 2024-01-31T12:16:56Z

Ok @dharmraj2018 a few more ideas:

Open the app, grant all permissions, but before clicking start, in a new terminal, run the following command:

adb logcat | grep -i WHS_PermissionPolicy

Now click start and see what is printed in the logcat, this might help us narrow down if the app is losing a permission at runtime. Paste the results back here.

Let's try updating Wear Health Services, to see if this is an issue that has already been fixed. Run the following command to open the playstore listing for WHS, since you're on an old version there should be an update available. Install it then run the following command to see the new version:

adb shell dumpsys package com.google.android.wearable.healthservices | grep versionCode

Report the new versionCode here, then repeat steps in 1)

Maybe there's a new system update available for your device in which this bug has been fixed. Check in your settings if this is the case, if there is an update, install it, rerun the steps in 1) and post the version from settings here.
I noticed in your video, GPS is unavailable so this might be the problem permission, to rule it out first open Google maps, ensure you get a GPS fix for the watch and then rerun the app but ensure the Prepare fragment shows that GPS has been acquired. Once GPS has been acquired rerun steps in 1)

dharmraj2018 · 2024-02-06T13:15:57Z

Thanks, @amankhoza! I've identified the issue; it seems that GPS was not enabled, leading to the crash on the Samsung watch. I resolved the problem by enabling the location before starting an exercise, and now the crash has been fixed.

yschimke · 2024-02-06T14:46:08Z

That sounds like a bug we could easily reproduce and fix.

monteiro-renato · 2024-02-21T19:33:05Z

Hello 👋
I had a similar issue today with a different setup.
I'm running Wear OS 3.5 on a TicWatch Pro 3 Ultra.
I was following the docs but instead of only trying out the HR functionality, I tried all the available options.
i.e. instead of:

val passiveListenerConfig = PassiveListenerConfig.builder()
    .setDataTypes(setOf(DataType.HEART_RATE_BPM))
    .build()

I configured:

val passiveListenerConfig = PassiveListenerConfig.builder()
                .setDataTypes(
                    passiveMonitoringClient.getCapabilities()
                        .supportedDataTypesPassiveMonitoring
                )
                .build()

While running the app I ended up with:

FATAL EXCEPTION: main
Process: x.y.z, PID: 6446
java.lang.SecurityException: Missing permissions
at androidx.health.services.client.impl.internal.StatusCallback.onFailure(StatusCallback.kt:43)
at androidx.health.services.client.impl.internal.IStatusCallback$Stub.onTransact(IStatusCallback.java:74)
at android.os.Binder.execTransactInternal(Binder.java:1159)
at android.os.Binder.execTransact(Binder.java:1123)
Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [StandaloneCoroutine{Cancelling}@d8e3de1, Dispatchers.Main.immediate]

After looking into health-services permissions
I noticed I was missing the ACTIVITY_RECOGNITION permission.
It would be nice if the exception could drive the user towards the solution.

If an exercise is started with incorrect permissions or location is disabled and it is being requested, WHS throws an exception, this was not being handled in HealthServicesRepository which resulted in a crash when calling startExercise. This change catches the error and displays it in an error screen. Implemented in ExerciseScreen to avoid having to reimplement the error catching logic since starting an exercise is called from multiple places. Prevents crashes like the one seen in android#212.

amankhoza · 2024-02-26T12:24:28Z

@monteiro-renato improving the exception has been raised internally, feel free to raise it as a public issue here if you want to keep track or get others to upvote etc. https://issuetracker.google.com/issues/new?component=1056301&template=1581114

In terms of the crash, I added a PR to prevent it for ExerciseSampleCompose in #231, something similar can probably be done for ExerciseSample.

If an exercise is started with incorrect permissions or location is disabled and it is being requested, WHS throws an exception, this was not being handled in HealthServicesRepository which resulted in a crash when calling startExercise. This change catches the error and displays it in an error screen. Implemented in ExerciseScreen to avoid having to reimplement the error catching logic since starting an exercise is called from multiple places. Prevents crashes like the one seen in android#212.

gitusman · 2024-10-17T09:11:16Z

I am facing similar issue. Getting same Missing Permission error, but I alraedy have ACTIVITY_RECOGNITION permission there, and other 4. Now I dont know which permission is missing...
I have checked in Settings > Apps > myApp > Permissions, all permissions are Allowed there.
Also, now when I uninstall and reinstall the app, it doesn't even ask for Permissions and assumes that I have denied them.. :/
What's going on with Android?

gitusman · 2024-10-18T17:45:27Z

I am facing similar issue:

https://stackoverflow.com/questions/79103144/wearos-startexercise-is-giving-missing-permission-error

breanatate · 2024-10-18T18:40:58Z

Hey @gitusman If you're using ExerciseSample, can you make sure you have Location enabled on the device? In the emulator this is, Settings > Location > Use Location. I'm not sure how it appears on Galaxy Watch, but it should be similar. This would be device settings, not the settings of the app.

gitusman · 2024-10-18T19:01:07Z

@breanatate Yes I am using the code of ExcerciseSample. Location was not enabled before. But I enabled it from the settings and tried again, still getting the crash

TimurVa · 2024-11-05T09:17:37Z

There is bug with PassiveData sample. Without
uses-permission android:name="android.permission.BODY_SENSORS_BACKGROUND"
It will never start the listener on boot_completed intent, so I suggest to add that permission it tooks quite a long time to recognize which permission I'm missing. It's getting error inside HealthServicesManager registerForHeartRateData for setPassiveListenerServiceAsync (java.lang.SecurityException Missed permission)

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Missing permissions on targetSdk 33 #212

Missing permissions on targetSdk 33 #212

dharmraj2018 commented Jan 8, 2024

yschimke commented Jan 8, 2024

dharmraj2018 commented Jan 8, 2024

yschimke commented Jan 8, 2024

dharmraj2018 commented Jan 8, 2024 •

edited

Loading

ithinkihaveacat commented Jan 8, 2024

dharmraj2018 commented Jan 8, 2024

yschimke commented Jan 8, 2024

ithinkihaveacat commented Jan 9, 2024

yschimke commented Jan 9, 2024

dharmraj2018 commented Jan 12, 2024 •

edited

Loading

ithinkihaveacat commented Jan 12, 2024

dharmraj2018 commented Jan 15, 2024

amankhoza commented Jan 26, 2024

amankhoza commented Jan 26, 2024

yschimke commented Jan 26, 2024

dharmraj2018 commented Jan 30, 2024 •

edited by yschimke

Loading

yschimke commented Jan 30, 2024 •

edited

Loading

amankhoza commented Jan 30, 2024

dharmraj2018 commented Jan 31, 2024 •

edited

Loading

amankhoza commented Jan 31, 2024

dharmraj2018 commented Feb 6, 2024

yschimke commented Feb 6, 2024

monteiro-renato commented Feb 21, 2024

amankhoza commented Feb 26, 2024

gitusman commented Oct 17, 2024 •

edited

Loading

gitusman commented Oct 18, 2024

breanatate commented Oct 18, 2024

gitusman commented Oct 18, 2024

TimurVa commented Nov 5, 2024 •

edited

Loading

Missing permissions on targetSdk 33 #212

Missing permissions on targetSdk 33 #212

Comments

dharmraj2018 commented Jan 8, 2024

yschimke commented Jan 8, 2024

dharmraj2018 commented Jan 8, 2024

yschimke commented Jan 8, 2024

dharmraj2018 commented Jan 8, 2024 • edited Loading

ithinkihaveacat commented Jan 8, 2024

dharmraj2018 commented Jan 8, 2024

yschimke commented Jan 8, 2024

ithinkihaveacat commented Jan 9, 2024

yschimke commented Jan 9, 2024

dharmraj2018 commented Jan 12, 2024 • edited Loading

ithinkihaveacat commented Jan 12, 2024

dharmraj2018 commented Jan 15, 2024

amankhoza commented Jan 26, 2024

amankhoza commented Jan 26, 2024

yschimke commented Jan 26, 2024

dharmraj2018 commented Jan 30, 2024 • edited by yschimke Loading

yschimke commented Jan 30, 2024 • edited Loading

amankhoza commented Jan 30, 2024

dharmraj2018 commented Jan 31, 2024 • edited Loading

amankhoza commented Jan 31, 2024

dharmraj2018 commented Feb 6, 2024

yschimke commented Feb 6, 2024

monteiro-renato commented Feb 21, 2024

amankhoza commented Feb 26, 2024

gitusman commented Oct 17, 2024 • edited Loading

gitusman commented Oct 18, 2024

breanatate commented Oct 18, 2024

gitusman commented Oct 18, 2024

TimurVa commented Nov 5, 2024 • edited Loading

dharmraj2018 commented Jan 8, 2024 •

edited

Loading

dharmraj2018 commented Jan 12, 2024 •

edited

Loading

dharmraj2018 commented Jan 30, 2024 •

edited by yschimke

Loading

yschimke commented Jan 30, 2024 •

edited

Loading

dharmraj2018 commented Jan 31, 2024 •

edited

Loading

gitusman commented Oct 17, 2024 •

edited

Loading

TimurVa commented Nov 5, 2024 •

edited

Loading