Status Update
No update yet.
Comments
al...@google.com
Can you attach / share a project that reproduces the issue?
lo...@gmail.com
because just occur recyclerview inside viewpager2 with constraintlayout, if paging3 use Independently with viewpage2 it's not problem.
lo...@gmail.com
al...@google.com
lo...@gmail.com
od...@google.com
Hey Louis thanks for reporting this, looks like a real bug - rest assured we certainly don't want anyone to need to apply device-specific workarounds!
It's not working fine on the Pixel Watch 2… BUT
Did you mean that it is working fine (asking because of the BUT)? If it's not working fine - can you share a video of that too? I haven't been able to reproduce it on Pixel Watch 2, so I want to know if you experience something else.
What is issue
? b/308759198
It's for internal tracking, no need to worry about that.
Thanks again!
od...@google.com
So it's a documentation problem?
I think the misunderstanding is that you want to reference the chosen option, and using .0 refers explicitly to the first option (not the chosen one). Does that make sense?
od...@google.com
I also reproduced this on GW6 Wear 4.
lo...@gmail.com
Did you mean that it is working fine (asking because of the BUT)? If it's not working fine - can you share a video of that too?
It's working fine on my Pixel Watch 2, the BUT was for the Samsung Galaxy Watch 4+.
I think the misunderstanding is that you want to reference the chosen option, and using .0 refers explicitly to the first option (not the chosen one). Does that make sense?
The documentation says those indexes are for the colors attribute since it can have multiple colors (a palette 🎨, essentially), it's not saying that it's for the declared option. In my case, I had only one color per palette, but I didn't expect it to change the behavior and lead to the behavior I showed initially on my Pixel Watch 2 (which looks similar to what the Samsung Galaxy Watch 4 is doing BTW).
Has there been misunderstanding between Samsung and Google on the format and documentation as well? 🤔
od...@google.com
Assigning to Garan for the documentation concern while we're looking into the bug.
al...@google.com
We have reported this bug to Samsung, they have been able to reproduce it and are investigating.
ga...@gmail.com
ga...@google.com
In addition to the clarification on usage of color index, there is an issue with switching the background color in Scene, a fix will be released in a future version.
For now, as a workaround you can use a PartDraw drawing a Ellipse or Rectangle which covers fullscreen with tintColor="[CONFIGURATION.bg]".
Description
Hello,
I'm puzzled by that one. The watch face where I get the bug is
first-release.apk. The same kind of configuration works incrop-release.apk.What is happening? Why is it working on the other watch face?
You can see the XML in Android Studio by drag'N'dropping the apk in any open project and looking at
res/li.xml.I have no clue how to debug this also, there's no information about that online, and it seems like the bug is in the renderer which I can't control anyway.
Help will be greatly appreciated.
Have a nice day!
Louis CAD