Hi Ron, thanks for the assistance. As you can see in the above screenshot, i left the same version number (and this shouldn’t be an issue), while updating the build number. I’m aware of this rules, since I develop apps for work
but I’m approaching the watchfaces world just lately. I have no idea of how i could proceed, my guess is that, since I’m updating a WearOS app (the watchface) using a smartphone compatible app (the companion app) something breaks, even if i have the WearOS release track active (using the same aab I’m trying to update in the smartphone release track). I’m probably missing something stupid, since I can’t seem to find solutions to this issue, and in my experience, when this happens, there’s a silly error on my side ._.