Watchface compiled with 4.2.1 cannot read bodybattery on a real device

Ah, ok. Thanks for your reply. By the way, from the feedback I'm getting it looks like the problem with 4.2.x likely affects only ASIA devices. Reported on:

FOREATHLETE 745 10.40(76f70fb)

fenix 6X Pro ASIA Solar 24.10

Instict 2 Solar Tactical 10.10 (6bd1a0a)

I have also found that apparently these features actually do work, but the "has" operator does not work on them.

So for example (ActivityMonitor.Info has :respirationRate) is false, but respirationRate delivers valid data.

Ah, ok. Thanks for your reply. By the way, from the feedback I'm getting it looks like the problem with 4.2.x likely affects only ASIA devices. Reported on:

FOREATHLETE 745 10.40(76f70fb)

fenix 6X Pro ASIA Solar 24.10

Instict 2 Solar Tactical 10.10 (6bd1a0a)

I have also found that apparently these features actually do work, but the "has" operator does not work on them.

So for example (ActivityMonitor.Info has :respirationRate) is false, but respirationRate delivers valid data.

yes . I think you're right. it just affect Asia models. as the system version is not the same (eg. ver 25.00 for non-asia but 25.10 for Asia ) and the latest device eg. fr255, fenix7 , the version is the same, and the bug won't appear. I have done all the special code , it seems works well.

Yes, I found that too. The problem is you must hard code skipping the has check for the problematic devices only, otherwise it will cause a crash on the devices that really don't have it. So that's not really a solution going forward. Based on the feedback I receive so far, it seems that only Asia models are affected (I never got it reported from a non-Asian product).

yes,it works ,without the has judgement, it works well . and now next step is findout how many devices has the issue

I found that if I sideload an app, it works fine,but I publish the same code on the store, it can't read.

maybe I can try to avoid the has check ,and publish it to see if it works

I am not sure if it merely occurrs on APAC devices. Never fully believe garmin ciq team. Prefer using a stable SDK.