Fixed
Status Update
Comments
da...@google.com <da...@google.com> #2
Thanks for the report. I will route this to the appropriate internal team and update this when I hear back from them.
ap...@google.com <ap...@google.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.
da...@google.com <da...@google.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"
Description
Component used: Fragment Version used: Devices/Android versions reproduced on:
When using Hilt Jetpack integration, the Hilt Work factory failed to create Worker with the following exception:
It appears this is due to a but in the class name mapping.
I declared my worker inside a Kotlin object like this:
Which create a
com.example.webservices.Device.Worker
entry in the Worker Factory mapping. But this entry do not match the real runtime class name which iscom.example.webservices.Device$Worker