I've been working on a simple watchface and run into an issue.
I work between 2 machines, a windows machine and a macbook pro 13. I work via the CLI tools, and have been incrementally working on a watchface thats mostly text based.
Everytime I add something to the watchface (such as steps, or modifying the css to change the look of it) I commit the changes to git and move on.
A few days ago I'd finished working on something in Windows, it was working fine on my Versa so I committed the changes and stopped working. Today, I pulled those changes to my macbook pro, built and installed the watchface on my watch and it is running (you can see the debug on the command line), but the svg/css isn't loading - so the watchface is blank.
Puzzled, I reset and cleaned my work area, reinstalled the environment with npm and rebuilt. Same issue. Thinking it might be a mac issue, I go back to my PC, rebuild and sideload - blank again.
After going back in time and checking out older, simpler versions of the watchface I still get blank on the watch for both windows and macos. I'm stumped. Any suggestions?
I do get 2 warnings, about settings and companion files... but I've had those from day 1 as I don't really need either right now.
Just loaded the watchface into the simulator, and works fine on there. Any suggestions on what could be wrong with sideloading to my watch? Any way of eeking more information out of the watch when it loads a sideloaded app? My watch is a versa, fully updated, paired with a OnePlus 6T. This worked a few days ago.
Just noticed the Fitbit app was updated yesterday too. 😕
