Status Update
Comments
le...@gmail.com <le...@gmail.com> #2
Thanks for the report. I will route this to the appropriate internal team and update this when I hear back from them.
ma...@google.com <ma...@google.com> #3
gr...@gmail.com <gr...@gmail.com> #4
"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"
on...@gmail.com <on...@gmail.com> #5
jo...@google.com <jo...@google.com> #6
+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
sd...@gmail.com <sd...@gmail.com> #7
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
jo...@google.com <jo...@google.com> #8
I'm really afraid Android 13 might get released as-is, breaking WearOS app communication 😨😨
no...@gmail.com <no...@gmail.com> #9
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.
jo...@google.com <jo...@google.com> #10
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!
le...@gmail.com <le...@gmail.com> #11
@
Thank you for the update @
jo...@google.com <jo...@google.com> #12
Android 13 is out today and we still have no patch unlike what you said a month ago
da...@gmail.com <da...@gmail.com> #13
fe...@gmail.com <fe...@gmail.com> #14
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
ha...@gmail.com <ha...@gmail.com> #15
- The report is 2 months old
- Google chose to release Android 13 with that bug
- There's no mention of this bug on the documentation so you can totally bump your targetSdk without noticing it
So thank you guys for working on this but it's still not a valid excuse for taking that long for such an important issue. Now that being said, let us know when a fix is available
le...@gmail.com <le...@gmail.com> #16
ka...@gmail.com <ka...@gmail.com> #17
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.
hu...@gmail.com <hu...@gmail.com> #18
us...@techtraits.com <us...@techtraits.com> #19
jg...@google.com <jg...@google.com> #20
jg...@google.com <jg...@google.com> #21
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.
el...@gmail.com <el...@gmail.com> #22
ch...@pushbullet.com <ch...@pushbullet.com> #23
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
Appreciate all the feedback and patience.
zz...@verus.io <zz...@verus.io> #24
[Deleted User] <[Deleted User]> #25
Hey @com.google.android.gms:play-services-wearable:18.0.0
.
After 4 months of testing, it looks like it's broken.
Description
1. Run the attached files in the dev_appserver and visit the local URL.
2. Upload the app to appspot and view it there.
What is the expected output? What do you see instead?
Both outputs should be the same. The dev_appserver works correctly, responding to the DELETE
request with "delete()". Appspot responds to the DELETE request with a "501 Not Implemented"
error.
What version of the product are you using? On what operating system?
App Engine SDK 1.1.1, Safari 3.1.2 and Firefox 3.0 on Mac OS X 10.5.4
Please provide any additional information below.
This issue seems to be elusively intermittent. When I originally started implementing an example
of this issue, DELETE XMLHttpRequests succeeded. Upon making the example match more
closely to my production code where the issue arose, I was able to reproduce the issue.
However, upon reverting to the earlier, working code, the issue remained.