Assigned
Status Update
Comments
lu...@gmail.com <lu...@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.
ra...@gmail.com <ra...@gmail.com> #3
One more detail, Data Layer event calls from the watch to the phone (running Android 13) do work on if the listener is in an Activity or Fragment.
g....@gmail.com <g....@gmail.com> #4
Also, I'm seeing this message in the Logcat:
"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"
"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"
sl...@gmail.com <sl...@gmail.com> #5
Experiencing the same issues, please see my other report for any useful logs:
https://issuetracker.google.com/issues/235673375
ma...@google.com <ma...@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
am...@gmail.com <am...@gmail.com>
re...@gmail.com <re...@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
do...@gmail.com <do...@gmail.com> #8
I'm really afraid Android 13 might get released as-is, breaking WearOS app communication 😨😨
Description
middleware, so that we could be able to plug it into
any of the Python frameworks that GAE supports. It would also be great
to have datastore-backed request.session setters and getters in the
webapp framework that GAE provides.