IssueTracker

lblb636@ Thanks for reporting this bug. I just want to confirm that the issue is the call device button being not responsive according to the uploaded video. It seems like this issue only happened on Windows.

Another similar issue that's related https://b.corp.google.com/issues/226426377

RE#4 I need to try this on Windows laptop first and I couldn't repro on MacOS or Linux. But I think this is most likely related to the modem simulator we introduced for API 31. Will need to further investigate.

I reproduced this bug on Windows with emulator version 31.2.10-8420304

Found the root cause when the "call device" button was unresponsive. It became unresponsive because the inbound call failed to initialize. Basically, the modem simulator's shared FD failed. When receive_inbound_call is invoked, it is supposed to make connection to the "host server" via a shared fd but it is flaky on Windows unfortunately.

modem-simulator: receive_inbound_call:101 inbound call from 6505551212
modem-simulator: process_msgs:296 waiting for new messages ...
modem-simulator: main_host_thread:501 got connection at host server at 65094
modem-simulator: start_calling_thread:254 making a connection to main host server 65094
modem-simulator: main_host_thread:507 Detected close from the other side
modem-simulator: start_calling_thread:262 nothing read quit
modem-simulator: main_host_thread:494 looping at main host server at 65094
modem-simulator: start_calling_thread:284 done with this thread

RE#12 I have uploaded a patch to fix this issue. I don't think it's the same reason for https://issuetracker.google.com/issues/233123301

RE#14 This issue is for API 31+, I will check for API 32 and API 33. Thanks for reminding me.

The fix has been merged in both 31 release and 32 release for since 05/2022.

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