WearableListenerService broken in Android 13 [235538840]

Fixed

Bug

Status Update

No update yet.

Description

kr...@gmail.com

created issue #1

Jun 10, 2022 09:57PM

WearableListenerService does not work when targeting Android 13. I'm guessing it's related to the behavior changes to Intent Filters:

https://developer.android.com/about/versions/13/behavior-changes-13#security

Sample app:

https://drive.google.com/file/d/1-oPBPKljEQwrc7YjDJaWcrHxfQBqJT_j/view?usp=sharing

Install both the phone and watch app then open the phone app. In the Logcat of the phone app you should see "test" outputted. If the target SDK is set to 32, you will see the message.

Phone Bug Report:

https://drive.google.com/file/d/10N8CFM_WxYT45qUBy5buj3TbexgYO2P8/view?usp=sharing

Watch Bug report:

https://drive.google.com/file/d/10MdnmLjp7IbSq0349yzxKkpBf8WkdGBb/view?usp=sharing

This has been tested on:

Pixel 5
Android 13 Beta 3.
WearOS 2.34
WearOS System Version: H M2

Comments

fl...@google.com <fl...@google.com> #2Jun 12, 2022 04:20PM

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

Android build
Which Android build are you using? (e.g. OPP1.170223.012)

Steps to reproduce
What steps are needed to reproduce this issue?

Please provide sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.

Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)

Screen record of the issue, for clarity
Please capture screen record or video of the issue using following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Attach the file to this issue.

NOTE : To avoid leaking private information, please share screenshots and bugreports only in Google Drive. Share files with android-bugreport@google.com and include only Google drive links in your bug. Bug report attachments should not be included directly in issue reports.

kr...@gmail.com <kr...@gmail.com> #3Jun 12, 2022 10:42PM

Android 9 on Nokia 7 Plus
Build number 00WW_3_54H_SP03

Android Studio 3.5.1 on macOS 10.13.6
compileSdkVersion 29
buildToolsVersion '29.0.2'
minSdkVersion 17
targetSdkVersion 28
implementation 'androidx.biometric:biometric:1.0.0-rc01'

Code taken from "Allow for fallback to non-biometric credentials" in

https://developer.android.com/training/sign-in/biometric-auth

Problem:
1. Show biometric prompt.
2. Tap "USE PASSWORD" instead of scanning fingerprint.
3. Unlock using pattern.
4. Activity stops responding.
See attached MP4 video.

This happens consistently.

Project attached in MyApplication.zip

kr...@gmail.com <kr...@gmail.com> #4Jun 12, 2022 10:49PM

Same issue with androidx.biometric:biometric:1.0.0-rc02

Android 9 on Nokia 7 Plus
Build number 00WW_3_54H_SP03

Android Studio 3.5.1 on macOS 10.13.6
compileSdkVersion 29
buildToolsVersion '29.0.2'
minSdkVersion 17
targetSdkVersion 28
implementation 'androidx.biometric:biometric:1.0.0-rc02'

Code taken from "Allow for fallback to non-biometric credentials" in

go...@stijnvandewater.nl <go...@stijnvandewater.nl> #5Jul 6, 2022 05:19PM

I am facing the exact same issue.

Android 9 on Moto Z2 Play (XT1710-07)
Build number PPS29.133-30

Android Studio 3.5.1 on Windows 10 Pro
compileSdkVersion 28
buildToolsVersion '28.0.3'
minSdkVersion 23
targetSdkVersion 28
implementation 'androidx.biometric:biometric:1.0.0-rc02'

be...@gmail.com <be...@gmail.com> #6Jul 15, 2022 09:31AM

Issue is reproducible. More details are here -

https://drive.google.com/open?id=1DoJlZ4WtmgbEPhH2HxNRsxLaG2MHL2b3 (internal only link)

be...@gmail.com <be...@gmail.com> #7Jul 15, 2022 09:38AM

I don't know what this is abou?

On Tue, Nov 5, 2019, 3:19 AM <buganizer-system@google.com> wrote:

- Show quoted text -

lo...@gmail.com <lo...@gmail.com> #8Jul 15, 2022 03:14PM

This error case appears to be triggered by creating BiometricPrompt immediately before calling authenticate(), rather than recreating the prompt in the Activity's onCreate() (or Fragment's onCreateView()) lifecycle method as intended. That's obviously an easy mistake to make, so I'll work on making sure the documentation is clearer here.

The fact that the activity appears to hang afterward is definitely a bug and will be fixed by aosp/1151594, likely in a 1.0.1 bugfix release. For now, I'm closing this bug as a duplicate of

b/143683687

be...@gmail.com <be...@gmail.com> #9Jul 15, 2022 03:21PM

Correction:

b/143091227

ks...@google.com <ks...@google.com> #10Jul 15, 2022 03:34PM

Must it be in onCreate?

I'm doing this in onResume instead of onCreate so that the prompt shows up when the user comes back to my app.

lo...@gmail.com <lo...@gmail.com> #11Jul 15, 2022 08:18PM

Project: platform/frameworks/support
Branch: androidx-master-dev

commit df08869e2c6f2d066f1caf143cebdb965c1b5a2c
Author: Curtis Belmonte <curtislb@google.com>
Date: Mon Nov 18 15:17:00 2019

Fix BiometricPrompt + device credential error case

BiometricPrompt currently has a bug in the following usage scenario:
1. The prompt is not instantiated in onCreate() or onCreateView()
2. Device credential auth is enabled with setDeviceCredentialAllowed()
3. authenticate() is called twice in the same activity/fragment

When this happens, the handler bridge is incorrectly reset before the
handler activity can be launched, preventing the prompt from being shown
at all. While this isn't a recommended usage pattern for
BiometricPrompt at the moment, it still shouldn't cause the prompt to
get stuck in this state. This commit therefore ensures that the above
scenario no longer triggers the bug.

Test: Manually, using sample app from

b/143097321

Test: ./gradlew biometric:test
Test: ./gradlew biometric:connectedAndroidTest

Fixes: 143097321
Change-Id: Ie7e343d9323437d9765e512a09a0e25a6c86dd8e

M biometric/src/main/java/androidx/biometric/BiometricPrompt.java
M biometric/src/main/java/androidx/biometric/DeviceCredentialHandlerActivity.java

https://android-review.googlesource.com/1168851

be...@gmail.com <be...@gmail.com> #12Aug 15, 2022 06:54PM

Yes, initializing the prompt in onResume() should be fine as well.

Unmarked as duplicate, since aosp/1168851 should be a more proper fix for this. Targeting it for inclusion in 1.0.1.

go...@stijnvandewater.nl <go...@stijnvandewater.nl> #13Aug 17, 2022 05:49PM

The following changes were cherrypicked through Coastguard (

https://android-build.googleplex.com/coastguard/)
Release Track: (

https://android-build.googleplex.com/coastguard/dashboard/5176090922385408/#/history/all)
Created: 2019-11-26 18:05:22.006209+00:00
Changes: aosp/1168851

ks...@google.com <ks...@google.com> #14Aug 17, 2022 06:42PM

I believe I am facing a related issue. I am using BiometricPrompt with setDeviceCredentialAllowed. This is fully working on an older device running Oreo (now that I recreate the activity each time after using BiometricPrompt). The user can choose to use their fingerprint to authenticate, or can select to use the pin. In both cases, once the user successfully authenticates, onAuthenticationSucceeded is called on the BiometricPrompt.AuthenticationCallback.

However when used in the emulator, running Android 10, as soon as the user selects the "Use PIN" option, onAuthenticationError is called with errorCode=5 and errString=Authentication canceled

be...@gmail.com <be...@gmail.com> #15Aug 17, 2022 08:14PM

Yes I am facing the same issue. Once I get the errCode = 5, the activity starting acting very strange. It then again gives an errCode = 10 before crashing again.

kr...@gmail.com <kr...@gmail.com> #16Aug 17, 2022 09:24PM

Google will come through. They always do!

be...@gmail.com <be...@gmail.com> #17Aug 30, 2022 02:41AM

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.

ga...@chargepoint.com <ga...@chargepoint.com> #18Aug 30, 2022 12:23PM

Is there an update on by when can we expect a fix for this? We are blocked on the app release which is targeting Android 13. We can't roll out if it doesn't support wear os app.

[Deleted User] <[Deleted User]> #19Sep 19, 2022 07:03AM

@Google Any updates here?

kr...@gmail.com <kr...@gmail.com> #20Sep 19, 2022 12:44PM

I have to imagine this needs to be fixed, at least, for the launch of the Pixel Watch.

be...@gmail.com <be...@gmail.com> #21Sep 19, 2022 12:47PM

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.

[Deleted User] <[Deleted User]> #22Sep 19, 2022 12:51PM

Well, according to

https://issuetracker.google.com/issues/235538840#comment14 the fix must be in testing for over 5 weeks now. I guess it should be done soon™ /s.

ks...@google.com <ks...@google.com> #23Sep 20, 2022 08:50PM

Marked as fixed, reassigned to ks...@google.com.

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.

ru...@gmail.com <ru...@gmail.com> #24Oct 17, 2022 02:58PM

WearableListenerService doesn't react on data changes after updating to sdk 31

be...@gmail.com <be...@gmail.com> #25Oct 23, 2022 01:04PM

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.

kr...@gmail.com <kr...@gmail.com> #26Oct 23, 2022 01:43PM

It's something on your end because the fix works.

be...@gmail.com <be...@gmail.com> #27Oct 23, 2022 01:46PM

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

lo...@gmail.com <lo...@gmail.com> #28Oct 23, 2022 01:50PM

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

be...@gmail.com <be...@gmail.com> #29Oct 23, 2022 01:53PM

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

be...@gmail.com <be...@gmail.com> #30Oct 23, 2022 01:56PM

Sorry, wrong link:

lo...@gmail.com <lo...@gmail.com> #31Oct 23, 2022 07:02PM

It's weird. I checked the codebase, and I don't see why it'd not be working.

Are you 100% sure that the apk deployed was not an old one with the
old library version for example?
Since there's been some issues with that in past Android Studio versions
and AGP, and since I'm not sure if it's fully fixed and which versions did,
I'd try to run the clean Gradle task, and then run the install task from
command line, and also make sure you're not trying the wrong
buildType/variant.

Please keep us updated.

On Sun, Oct 23, 2022 at 3:56 PM <buganizer-system@google.com> wrote:

- Show quoted text -

be...@gmail.com <be...@gmail.com> #32Oct 23, 2022 07:35PM

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.

to...@gmail.com <to...@gmail.com> #33Oct 24, 2022 07:26AM

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

be...@gmail.com <be...@gmail.com> #34Oct 24, 2022 07:30AM

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.

lo...@gmail.com <lo...@gmail.com> #35Oct 24, 2022 09:13AM

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

sw...@gmail.com <sw...@gmail.com> #36Dec 21, 2022 07:36PM

Comment has been deleted.

Message last modified on Dec 23, 2022 05:04AM

li...@gmail.com <li...@gmail.com> #37Dec 24, 2022 02:02PM

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.

ol...@gmail.com <ol...@gmail.com> #38Jul 15, 2023 02:46AM

It was not fixed. As of today - the same problem: phone doesn't receive messages from a wearable device with API 33. API 31 works fine

ol...@gmail.com <ol...@gmail.com> #39Aug 20, 2023 04:24AM

Do we have any updates for this? Google pushes API 33 as mandatory in 11 days, but this bug doesn't allow me to upgrade.
=======
"Status
You won't be able to release app updates (11 days away)
Date sent
Aug 10, 2023
Deadline
Aug 30, 2023
Violation
App must target Android 13 (API level 33) or higher"

[Deleted User] <[Deleted User]> #40Sep 7, 2023 11:01AM

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.

ja...@gmail.com <ja...@gmail.com> #41Sep 21, 2023 03:45AM

We got the same issue and resolved by updating GMS to 18.1.0:
com.google.android.gms:play-services-wearable:18.1.0

ha...@gmail.com <ha...@gmail.com> #42Oct 23, 2023 03:24AM

targetSdk=33 and com.google.android.gms:play-services-wearable:18.1.0: STILL NOT OK😢

yf...@gmail.com <yf...@gmail.com> #43Nov 14, 2023 04:06PM

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

ch...@gmail.com <ch...@gmail.com> #44May 25, 2024 04:24PM

Has there been any update? Since targeting 33, I have experienced issues with the app's syncing ability (in production only).

da...@gmail.com <da...@gmail.com> #45Aug 26, 2024 04:30PM

1.1.5.2.5.2.5.1.5.4.4.2