Status Update
Comments
dy...@gmail.com <dy...@gmail.com> #2 Restricted
dy...@gmail.com <dy...@gmail.com> #3
because just occur recyclerview inside viewpager2 with constraintlayout, if paging3 use Independently with viewpage2 it's not problem.
dy...@gmail.com <dy...@gmail.com> #5
dy...@gmail.com <dy...@gmail.com> #7
dy...@gmail.com <dy...@gmail.com> #8
The issue has returned, & I have not side-loaded any applications, as was thought to be the cause previously. The issue appeared after a recent reboot. A Watch Face Format watch face was selected when the device was booted. Selecting another WFF watch face produces an error toast exactly like the video attached above. Selecting non-WFF faces will load normally. You can also force WFF faces to load & bypass the error toast by doing the following: select the face; when the error shows, immediately press the crown.
dy...@gmail.com <dy...@gmail.com> #9
I tried to add
ad...@google.com <ad...@google.com> #10
dy...@gmail.com <dy...@gmail.com> #11
Additional information from my own testing of this error:
2 scenarios seem to be consistent on my device:
(1) Fix errors:
-
Remove all saved watch face configurations from the carousel, except a single watch face that is NOT Watch Face Format.
-
Reboot.
-
Watch faces, including Watch Face Format watch faces, function as normal & do not present an error.
-
Adding additional faces does not result in any errors either.
(2) Reproduce errors:
-
Set a Watch Face Format watch face as the selected face being used.
-
Add at least one additional Watch Face Format customization to the carousel.
-
Reboot.
-
Change watch face to another saved selection. This first change operates normally.
-
Change to another Watch Face Format watch face, be it the original selection, a 3rd saved option, or loading a new face from the drawer.
-
The error toast is reliably reproduced.
-
Any subsequent WFF selections produce the error.
-
Non-WFF faces load as normally expected.
-
You can ALWAYS override the error & get the face to load by dismissing the toast quickly when it appears, which can be done by pressing the crown button.
od...@google.com <od...@google.com>
dy...@gmail.com <dy...@gmail.com> #12
Got the ping for the above. Really hope I can assist getting things straightened out with this error. Much love to the Wear OS team!! Please let me know if I can provide another bug report or anything for you to help.
lu...@google.com <lu...@google.com> #13
@dy...@gmail.com Can you please help me reproduce this issue? I have set a WFF watch face as my current one. What exactly do you mean by "Add at least one additional Watch Face Format customization to the carousel." - should this be the same watch face as the initial one, but edited differently, or should it be another WFF watch face?
Before rebooting, should I have more than 2 watch faces in my carousel? If so, should one of them be a pre-installed / non-wff watch face?
dy...@gmail.com <dy...@gmail.com> #14
Sure thing!
should this be the same watch face as the initial one, but edited differently, or should it be another WFF watch face?
Either of those scenarios result in errors for me.
Before rebooting, should I have more than 2 watch faces in my carousel? If so, should one of them be a pre-installed / non-wff watch face?
It seems to me that the issue is only dependent on the face that is set currently being WFF, but I'll test now & see if it errors with & without another WFF face saved in the carousel.
lu...@google.com <lu...@google.com> #15
I would be grateful if you could add a new bugreport here if you reproduce the issue again.
dy...@gmail.com <dy...@gmail.com> #16
Test 1:
The only face in the carousel is a Watch Face Studio built watch face format face. Nothing else in carousel. The single face is set, & I am rebooting. If it produces the error here now, i will record a bug report.
dy...@gmail.com <dy...@gmail.com> #17
I definitely reproduced some errors. A ton of instability, even beyond what I expected. It's quite unhappy at the moment, to the point it is hard to take a bug report. I will send one shortly when able.
dy...@gmail.com <dy...@gmail.com> #18
The watch entirely crashed on me and rebooted. 😅
lu...@google.com <lu...@google.com> #19
I'm sorry to hear this. I am installing the exact OS version you had in a previous bug report. Initially, Mohammad found an error which has been fixed for a while and I was expecting the fix to have been released. On a second bug report, I couldn't find it anymore.
I am trying to reproduce this on that exact same OS version from the bug reports and if I find the same error, then I will check the release pipeline.
dy...@gmail.com <dy...@gmail.com> #20
I'm mostly managing around this error without much problem. I just want to make sure that if this is something easily reproducible, it isn't hitting less experienced users that will be frustrated by it. I wanna squash the bugs with you!!
I have rebooted again & I'm giving it more of a moment to initialize at the moment.
I am currently on the latest updates, as far as I know, but a bug report will give you the full picture.
I'll return shortly.
dy...@gmail.com <dy...@gmail.com> #21
Yes, issue was reproduced as expected on this reboot.
Ignore the above that I had only one face set, because I set other faces before the crash, so i had several in the carousel on this reboot.
I launched the watch with a wff set.
I selected another wff from the carousel. THIS ONE WORKS NORMALLY. The first change always works fine.
I change to a 3rd wff. ERROR.
Collecting bug report now.
dy...@gmail.com <dy...@gmail.com> #22
View
lu...@google.com <lu...@google.com> #23
Perfect, thank you! This bug report indeed shows the error that I was expecting. We have already fixed it and it is scheduled to be released soon. I will make sure to get this out ASAP. I am sorry for the inconvenience.
dy...@gmail.com <dy...@gmail.com> #24
Great!! I'm so glad it is fixed! Always excited for new updates; thank you for your work!
Description
Attempted methods to remedy this that were all unsuccessful include:
Uninstalling updates to ProtoRender Layout, clearing app data, clearing the watch face carousel, & rebooting the device.
Repeating the above with side loading ProtoLayout Renderer (Wear OS) 1.2.224.561625265.
Resetting app data/uninstalling & reinstalling offending watch faces & repeating the above.
Reverting developer settings to factory state & repeating above.
Attached is a video of the error occurring. Notice that when I select the pixel art watch face, which is not based in the new Renderer, it is able to load. The stock faces are also able to load.