Thanks to your support, today we released new Beta version 1.3.8 (here)
This is Beta version for new features which will be introduced in SDC22 (here).
We will monitor bugs of the beta version by the end of October and finally distribute the user guide along with the public version in mid-November.
Please use it a lot and share it if you have any problems. I hope you pay a lot of attention to Beta version and SDC22.
I don’t know if this is the right place to post issues / improvement proposals so please move this to other thread if needed.
color customization - color highlights are misaligned in the “currently selected” color. Also, these color dots / circles have some messy / unequal edges. This needs better implementation because on the watch it doesn’t look good.
If there are multiple colors combined for one color style, separators or lets say, transitions between colors need to be more fluent (maybe stacked on each other?) to prevent these badly looking lines if the same color is used for different elements
Since I installed this new beta version, I am missing some options to appoint - in the Gear Wearable app once the watch face is installed on the watch - complications like the air pressure/barometer. Has something changed in this respect?
I am getting the below message usually when i am trying to build or send the watch face to the watch. After this message the build or transfer to watch always fails and a restart of the computer is required in order to be able to build again.
The triple color style is a nice addition, but it would be more useful if it is an independent 3 sets of color style customization (Or maybe we can dynamically create the color set). And treat it just like image styles that can be grouped into set if it needs to be a color combo combination. And also the label can be renamed, not just “Color”.
An additional limit for image styles to more than 10 is also a welcome addition. Usually, my watch face had up to 20 styles on Tizen.
Thank you for feedback.
This behavior is the same in public version which was distributed, not Beta version.
But you want to build with public version only, so it seems inconvenient because Beta version and public version cannot be used separately at the same time. We have fully verified Beta version, but we used the name ‘Beta’ for your additional general usability check.
We will make it possible to update to public as soon as possible.
The update to Wear OS One UI 4.5 was installed on my Galaxy Watch 5 pro on the 11th of September. I am very sure that after that update I was (still) able to select barometer as a complication. So I do not think that this update to Wear OS One UI 4.5 is related to this ‘glitch’.
EDIT: this is really odd. I changed the language on my phone (Galaxy S21 FE) from Dutch (NL) to ENG (US) and a lot more complications appeared as available (including the barometer). After having switched back to Dutch (NL) I can still select all the complications I could in ENG. So, for me this issue is resolved. However, it seems to be a bug. Where can I report this bug?
I’m curious if this was just a matter something in the Watch or the Wearable App when you changed languages.
In the future you can report bugs in the Samsung Members app. Even if it is a Wear OS issue they should handle it. If it was a Wearable App then for sure it is Samsung’s bug. If this was WFS issue then Catherina has seen it and you don’t need to report it as such.
The color style customization order always stays on the first order, although we already set the order on the customization editor.
And also we need to set the target API to the latest version, currently, the WFS target API is 30. Google now requires the minimum target API to be 2 versions from the latest, so it will need to be updated soon.
I have stumbled on something strange with the new beta.
I was trying to use textFormat function on [SEC_MSEC] tag, like numberFormat(00.000,[SEC_MSEC]).
For some reason I could not reach any formatting not even any real time msec values to be displayed in preview.
When I isolated the [SEC_MSEC] in the text field to see what it actually returns, there was comma in place of the decimal point. In my country we do use decimal comma so it first did not feel strange, but then I realized, this may cause variable mismatch for the formatting function and cant be processed right.