We are talking about missing ability to choose complication in wearable app?
yes, I tried GW5 pro updated to One UI 5.0 and GW6 which came with OneUI 5.0 there was no recent updates for either but I see all the complications. One watch face I know was built with WFS 1.3.13
Regarding the [DST] Tag I submitted a bug report but after doing some ICU reading I think the new Time Standard does not use it. When I tried [TMZN_ABB] instead it doesn’t work in the preview window. I’ll try that on the watch later today.
I used one watch face that I downloaded from the store and Mateo said it was developed with WFS 1.3.13 and I used my test watch face that I created that was developed with 1.5.7 and both showed all watch faces.
I am asking (suggesting) is if the watch faces that do not show any complications were developed with 1.2.x?
Yeah that is an old bug I originally asked about. I think the solution was to just download an app such as calendar, to your watch and they all appear after that. Or you could try force stop and restart Google Play Services on your mobile.
All watch faces made with WFS 1.4.19 and UP (1.4.20, 1.5.7) are using Watch Face Format.
Recent Galaxy Wearable update version: 2.2.57.23102461 introduced an issue where it is impossible to set custom complication from galaxy wearable app, all slots are showing “NONE”. This only affects Watch Face Format watch faces. WFS 1.3.13 is using bundled renderer.
I’ve already created support request for this.
I don’t know but sometimes it feels like coordination between Samsung and Google is really bad.
November comes and Google releases fixed phone companion app.
Few hours later Samsung releases new Galaxy Wearable app update with changelog: fixed the error. What happened? Samsung introduced same error which was there for Pixel Watches for about one month. So, all devs who are creating with latest WFS (1.4.20+) will now be receiving tons of negative reviews because people think it’s watch face error that complications can’t be customized directly from Galaxy Wearable app.
Worse part? We don’t know how long it will take Samsung to fix the issue.
@r.liechty_SDR , do you have some ability to highlight this issue or point at it as top priority? It needs to be fixed urgently, like… really urgently… Request number: #49205
Recent Galaxy Wearable update version: 2.2.57.23102461 introduced an issue where it is impossible to set custom complication from galaxy wearable app, all slots are showing “NONE”. This only affects Watch Face Format watch faces. WFS 1.3.13 is using bundled renderer.
I checked and I have the update pending. I canceled it.
I don’t know but sometimes it feels like coordination between Samsung and Google is really bad.
Yes that would be a bug; the ICU Time standard exemplars show it as being either PST or PDT but I checked and WFS does not show that at least in the preview window.
In the ICU Dates and Time there is Unicode format where you read the time string and parse it into various components. For example, *metazone* “America_Pacific” has its own display name data such as “PST” “PDT” “PT” “Pacific Standard Time” “Pacific Daylight Time” “Pacific Time” and these names are shared by multiple individual time zones
The string is v, vv , vvv for abbreviations and vvvv for the full time zone name.
That is why I think it might be a bug in how WFS is parsing the string.
It the screenshot i mean.
Hawaii-aleutian time = hat = hst?
Hawaii-aleutian daylight time = hdst?
I meant if the phone cant differentiate between normal time e.g hawaii-aleutian time and hawaii-aleutian daylight time why cant the abbreviation on watch?
So its the bug in icu library or wfs parsing?
If the bug is in icu then nothing samsung / google can do? If its wfs then should we report it as a wfs bug? That my question
-10 UTC local time zone abbreviation is HST and Daylight savings time would be HDT or just HT for the two letter abbreviation.
So its the bug in icu library or wfs parsing?
I assume this is WFS parsing of it but it could be the library that translates the time coordinates into the Unicode. Remember the German abbreviation for a month, that was the library.
Sense the tag IS_DST does not work one could assume that is the issue I need to see if [TMZN_ ABB] works on the watch it may just not work on the emulator. There is no Unicode for DST that is a local time zone name, I don’t know how they get it since it really is noon even if the clock says 13:00 in Daylight savings time.
By the way GMT has “summer time” so UTC universal time coordinate is what time zones are based on as well as navigation, etc… WFS should not use it that is a bug and pet peeve of mine.
