I’ve been experimenting a lot with the Pixel Watch Emulator in Android Studio. For the first time, I’m realizing that the built into WFS Weather Tag Expressions don’t function at all.
I just started making weather heavy faces, and now I’m realizing they’ll only work on a Galaxy Watch. According to Google, these Tag Expressions are coming directly from OneUI, and not WearOS.
Has anyone found a work around for this, other than Customizable Complications with a Weather App installed on the watch?
I don’t think it’s as simple as that. WFS converts its tags into standard WFF XML (including attribute data sources) when you publish a design in WFS. You can unzip the created file and inspect the WFF XML. If there’s a problem, it’s probably because WFF is not converting its tags to WFF correctly.
It’s actually possible to adapt WFF XML created by WFS to run in a Wear OS emulator with Android Studio. The process isn’t for the faint-hearted, but could be used to assess whether the created XML is valid. (However, I don’t think that emulator emulator emulates all data sources; I don’t know about weather.)
So the weather tags might actually work on a physical Pixel watch?
I’ve looked at those XML files. I wish someone would publish a WFF XML for Dummies book.
If I could understand them, I could write software to create and manipulate them. Parsing and Manipulating files is my jam. I written quite a few conversion tools through the years to get indifferent systems to be able to talk to each other.
I’m guessing that the WFF XML ‘tags’ work correctly. If WFS is bungling the conversion to WFF XML, then any relevant XML produced using WFS won’t work properly on any Wear OS device (Samsung, Google, emulator, etc). The best way to test this theory would be to inspect the XML, and maybe compare it with known correct and working code written directly in XML.
The emulator doesn’t emulate the complete environment. The weather-is-available tag (whatever it’s called) should indicate this. Are you checking that?