Fixed
Status Update
Comments
ze...@google.com <ze...@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.
ap...@google.com <ap...@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"
ap...@google.com <ap...@google.com> #5
Experiencing the same issues, please see my other report for any useful logs:
https://issuetracker.google.com/issues/235673375
Description
The resolution of b/151804585 did not introduce a new field backing, thus lookups within a class are linear search in the field arrays. This has noticeable performance impact witnessed in b/264430795
Using the dump information provided in b/264430795 , the initial regression came with CLs:
With the bottom CL being fairly equal in runtime to the original report at version 2.0.99.
Total regression is about ~1.5min on a previously 4.5min build (increase of about 33% in compiletime).
We should introduce a (potentially) hash-map based field collection backing mirroring the backing for methods.