Using Authenticated Browser Downloads on specific bucket when Data Access Audit Logs enabled [146211528]

In Progress

Feature Request

Status Update

No update yet.

Description

ar...@google.com

created issue #1

Dec 13, 2019 05:27PM

Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.

Problem you have encountered:

- Unable to download files from a GCS bucket that has Data Access Audit Logs enabled, using Authenticated Browser Downloads. it returns a 403 Error. This will work if the Data Access Audit Logs is disabled.

What you expected to happen:
- Enable users to have the Audit Logs enabled as well allowing access using Authenticated Browser Downloads

Steps to reproduce:
- Create a bucket and enable the Data Access Audit Logs and try using Authenticated Browser Download to download file from that specific bucket.

Comments

ar...@google.com <ar...@google.com> #2Dec 13, 2019 05:30PM

Assigned to gc...@google.com.

Thanks for the report. I will route this to the appropriate internal team and update this when I hear back from them.

al...@bendingspoons.com <al...@bendingspoons.com> #3Jun 3, 2022 02:01PM

Comment has been deleted.

Message last modified on Jun 3, 2022 04:54PM

ka...@google.com <ka...@google.com> Oct 10, 2022 12:15PM

Reassigned to ka...@google.com.

ka...@google.com <ka...@google.com> Jun 15, 2023 11:46AM

Accepted by ka...@google.com.

ka...@google.com <ka...@google.com> #4Jun 13, 2024 12:53PM

Also, I'm seeing this message in the Logcat:

"2022-06-12 18:47:15.156 1841-4562/? W/PackageManager: Intent does not match component's intent filter: Intent { act=com.google.android.gms.wearable.BIND_LISTENER"

fa...@axa.ch <fa...@axa.ch> #5Jul 2, 2024 03:14PM

Experiencing the same issues, please see my other report for any useful logs:

https://issuetracker.google.com/issues/235673375

fa...@axa.ch <fa...@axa.ch> #6Jul 16, 2024 06:38AM

+1, can confirm it doesn't work on Android 13:=

2022-07-15 11:26:15.023   589-5347  PackageManager          pid-589                              W  Intent does not match component's intent filter: Intent { act=com.google.android.gms.wearable.BIND_LISTENER cmp=xxx/xxx.WatchMessageReceiver }
2022-07-15 11:26:15.023   589-5347  PackageManager          pid-589                              W  Access blocked: ComponentInfo{xxx/xxx.WatchMessageReceiver}
2022-07-15 11:26:15.023   589-5347  ActivityManager         pid-589                              W  Unable to start service Intent { act=com.google.android.gms.wearable.BIND_LISTENER cmp=xxx/xxx.WatchMessageReceiver } U=0: not found

ay...@google.com <ay...@google.com> #7Jan 14, 2025 03:29PM

Note that I've been able to make it work by:

Adding <action android:name="com.google.android.gms.wearable.BIND_LISTENER" /> in the intent filter
Removing <data android:scheme="wear" android:host="*" />

But I feel like this is not something we should do