Hello,
A user with the Venu 2 Square Music Edition watch installed my watchface (Big-Tey: https://apps.garmin.com/en-US/apps/e48018f3-66c8-40dc-b1fc-8330520c389c) over a year ago and everything worked great. this past week, he purchased a new Venu 2 Square Music Edition and installed the Big-Tey watchface but it does not work on the new device. The watchface is displayed, and after 5 seconds the screen goes blank and does not turn on again.
The Big-Tey source code has a jungle file that divides builds into 2 code bases: Release (for new modern devices supporting API 4.0.0 and later) and Legacy devices (supporting APIs prior to 4.0.0). My jungle file specifies the Venu Sq 2 Music Edition (venusq2m) shall use the Release build (as it uses an API beyond 4.0.0). When I run the watchface in the emulator using the venusq2m, I can open my watchface's About menu and the Build Version is set to Release as expected. When my user runs the Big-Tey watchface on his old Venu Sq 2 Music Edition and checks the About screen, the build version is also set to Release (as expected). But magically, the build version on his new Venu Sq 2 Music Edition is set to Legacy.
The above should not be possible. The only way the Legacy version can be installed on the venusq2m is if the Connect-IQ App Store somehow mapped this version to his new device. But my jungle file explicitly maps the Release code to the venusq2m, which is just what we see on his old device and in the device emulator. The information for both devices is as follows:
- Device Type: Venu Sq 2 Music Edition (venusq2m)
- Device Firmware: 5.1.0
- Big-Tey Version: 2.0.13
- Big-Tey Connect-IQ Version: 8.1.1
I believe the Big-Tey watchface is not working on the new venusq2m device because the Connect-IQ App Store is downloading an incorrect Build, as is indicated by the fact the Build version shows as Legacy when it should be Release. Can anyone from the Garmin side or dev community help determine why this is happening and how to resolve the issue?
Thanks for your support!
