GCS UI - order by date, size + bucket info (size, count of files) [119209458]

Assigned

Feature Request

Status Update

No update yet.

Description

ya...@gmail.com

created issue #1

Nov 7, 2018 10:44PM

UI could be more user-friendly - see competition.
E.g.
- not easy to find the latest file being created or updated in a large bucket --> sort by
- add creation date, user (creator)
- filter by user, regex on name (and/or suffix)
...

The above can be done with the API set, or third-party browser - why not in console (+extend to Mobile).

Comments

kn...@google.com <kn...@google.com> #2Nov 9, 2018 02:41AM

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.

[Deleted User] <[Deleted User]> #3Dec 6, 2020 12:37AM

One more detail, Data Layer event calls from the watch to the phone (running Android 13) do work on if the listener is in an Activity or Fragment.

db...@tzero.com <db...@tzero.com> #4Jan 19, 2021 12:02PM

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"

w....@gmail.com <w....@gmail.com> #5Sep 1, 2021 01:19PM

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

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

[Deleted User] <[Deleted User]> #6Dec 1, 2021 05:28PM

+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

le...@pepkorit.com <le...@pepkorit.com> #7Nov 11, 2022 11:29AM

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

dz...@nsoft.com <dz...@nsoft.com> #8Feb 22, 2023 12:30PM

I'm really afraid Android 13 might get released as-is, breaking WearOS app communication 😨😨

he...@gmail.com <he...@gmail.com> #9Mar 10, 2023 03:49PM

If you're not targeting API 33 you're not affected by the bug. So it's a big bug, and yes we of course expected more from Google, but you can always target the api level later when it's fixed.

But I agree this is kind of desperating that more than 1.5 month after the first report nothing has changed.