Status Update
No update yet.
Comments
ra...@google.com
Thanks for the report. I will route this to the appropriate internal team and update this when I hear back from them.
r....@gmail.com
bi...@gmail.com
"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"
sa...@gmail.com
ra...@google.com
+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
bi...@gmail.com
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
sa...@gmail.com
I'm really afraid Android 13 might get released as-is, breaking WearOS app communication 😨😨
ra...@google.com
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.
ra...@google.com
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!
bi...@gmail.com
@
Thank you for the update @
ra...@google.com
Android 13 is out today and we still have no patch unlike what you said a month ago
Description
Starting on February 2nd, my application started receiving user generated bug reports regarding a crash related to the
I have not received any crash reports in Firebase Crashlytics because it appears to be happening not in our application, but in the "Photos & Videos" application. The app hadn't been updated in a while and these reports started flooding in all at once, leading me to believe it is an Android system issue.
The error happens when presenting the photo picker, it crashes immediately. The crash dialog from Android indicates the "Photos & Videos" app is having a problem, not my application. Here is a video of it happening.
I'm unable to reproduce this on any device I have across multiple Android versions. When asking users for more details, these are the details we get about impacted devices. It seems to be Android 13 related.
Model: Samsung Galaxy A71 Android SDK: 33 Device language: PT
Model: Redmi Note 11 Android SDK: 33 Device language: PT
Model: Samsung Galaxy S22 Android SDK: 33 Device language: PT