IssueTracker

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

+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

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

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

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.

As an interim update on this issue: we've been already working on the fix that should be available by Android 13 release. The fix requires thorough testing, I'll keep this bug updated as soon as we have more to share. Thanks!

@comment#9 The Play Store will eventually require targeting API 33, then 34, etc, so accepting this regression in a customer release would be a time ticking bomb for Wear OS apps.

Thank you for the update @comment#10

This issues has been already given high priority (updated external priority on this bug to reflect internal status). The fix is on the way and going through the final rounds of testing, so the roll out is slated to next couple of weeks.

To reiterate what have been mentioned earlier on this bug: this issue affects only apps targeting Android 13, so the apps won't break unless you bump targetSDK version to 33. In case if you want to start working on app compatibility for Android 13 behaviour changes, you could use Compatibility framework to toggle on/off the changes individually for isolated testing.

That must be some really intense testing as we are 10 days later and still nothing on sight. I don't want to be a P2 issue if that's what a P1 is.

My bet is that Google still targets API 32 (or even lower) internally so they don't care and didn't even saw the issue before our report.

This issue is fixed. The fix has been rolled out via GMSCore and will also require using the latest com.google.android.gms:play-services-wearable:18.0.0 release.

Note that you don’t need to add BIND_LISTENER manually, it has been deprecated for a long time and it continue to remain so (read more at https://android-developers.googleblog.com/2016/04/deprecation-of-bindlistener.html).

Appreciate all the feedback and patience.

Hey @comment#23 I can confirm the fix doesn't work. Tested on Pixel 6 Pro running Android 13 and a Pixel Watch running WearOS 3.5, things are working great if my app targets API 32 but doesn't when targetting API 33 using com.google.android.gms:play-services-wearable:18.0.0.

After 4 months of testing, it looks like it's broken.

Well that's possible but I've tested things carefully and targetting API 32 immediately fixes the behavior so I'm confident this is the root cause of the issue

Can you share the configuration code you have for the affected service from your AndroidManifest.xml file?

Sure thing, you can find them both in the commit that rolls back to targetting API 32: https://github.com/benoitletondor/PixelMinimalWatchFace/commit/604bdc2b640431a1216653c65f3bb86feda9a124

Sorry, wrong link:

• https://github.com/benoitletondor/PixelMinimalWatchFace/blob/release/2.2.0/android/companionapp/src/main/AndroidManifest.xml
• https://github.com/benoitletondor/PixelMinimalWatchFace/blob/release/2.2.0/android/watchface/src/main/AndroidManifest.xml

I don't think it's that, it was installed from PlayStore so it's a release one built from command line with a version bump

Maybe there was something wrong but all I did between this build and the new one is roll back to targeting API 32 and things worked immediately so it's strange to me.

As a reminder the fix require an update to Play Services on the device too.

Indeed I can see PlayServices aren't updated on my device, like on a lot of Android devices right now auto-update of apps is broken.

I'll try again with up to date services and I'll let you know.

But that means it's far from production ready as we can't expect all of our users to be up to date right now so I'm glad I rollbacked to API 32 for now.

Which Play Services version is supposed to fix it? We might add a check using PackageManager APIs to direct users to perform the update.

Have you taken into account the situation of Chinese devices? It's hard for them to upgrade the Play Service and there are no official solutions about this issue.

Issue is not yet solved, as we face the exact same problem still.

• Using targetSdk=31 and com.google.android.gms:play-services-wearable:18.1.0: OK
• Using targetSdk=33 and com.google.android.gms:play-services-wearable:18.1.0: NOT OK

When using targetSdk 33, messages are no longer sent from the wearable to the phone (e.g. WearableListenerService.onMessageReceived()) is no longer called.

You do not have the Arabic language. I am not fluent in English

1.1.5.2.5.2.5.1.5.4.4.2

+1

Exciting news! GCS Team is currently developing IP Filtering capabilities. This much-requested feature is targeted for release in Q2 2025 - Q1 2026. We'll provide more updates as development progresses.

There might be a bug in "Bypass bucket IP filtering rules".
Our co-worker find out storage.buckets.exemptFromIpFilter does not do anything with the filter. (still blocked even using the bypass feature)
Hope any googler see this and have a look on it.

https://cloud.google.com/storage/docs/bypass-ip-filter

w.r.t comment #152 I think you might misunderstand the actions allowed like I did initially.

Per Bypass bucket IP filtering rules:

Bypassing bucket IP filtering rules exempts users or service accounts from IP filtering restrictions for creating, deleting, or configuring buckets, while still enforcing rules for others.

The for creating, deleting, or configuring buckets part is important. The storage.buckets.exemptFromIpFilter permission allows you to update a bucket from an IP that is blocked, for example to update the blocked IPs if locked out. It does not exempt object get / put access from a blocked IP.

Thanks for the feature, we were waiting for it for a long time.

Is it planned to grant more permission to the storage.buckets.exemptFromIpFilter permission ? It would be really helpful to allow some users or service accounts to bypass the ip filter and to be able to get/put objects without having to deal with the ip filter.