• Replies 137 replies
  • Subscribers 27 subscribers
  • Views 17048 views
  • Users 0 members are here
Options
Related

Watchface compiled with 4.2.1 cannot read bodybattery on a real device

li2niu
over 1 year ago

As the title, I just compiled my watchface with SDK4.2.1. However some users told me the body battery became in-readable on their real devices. Everything works fine in my simulator.  Do you have similar issues?

  • over 1 year ago

    I've updated f6/f7 sim devices and have built my wf with 4.2.2, and there is no any problem with bb on device (25.10/11.28).

    attached screenshot from enduro1 and it is the same like f6.

    So question is: is safe to compile with 4.2.2 and publish it? Has anybody tested 4.2.2?  Which model had a problem with the bb?

  • over 1 year ago in reply to _psx_

    I have a bold idea, depend on these:

    1.  it works well when I complied with sdk 4.2.1 and and sideload in Enduro 1/Fenix 6, but it didnt work when I exported it and upload to the garmin server.

    2. I wonder if  garmin server will  re-complie the watchface when I uploaded them?

    if the 2nd point is true , consider it with the 1st point , I doubt that the garmin server have fixed the bug when you uploaded the watchface built with 4.2.2. It also explained why it doesn't work when  upload his watchface built with 4.2.2 and failed to work, because at that time ,the server bug is not fixed yet .

    in all these , "work" means getting the bodybattery value.

  • over 1 year ago in reply to nnkn

    Point 2 is false.  When you build an iq file for the store, there is no source code included, so there is no way Garmin can re-compile the app

  • over 1 year ago in reply to jim_m_58

    point 2 should be false of course

    so maybe problem was with firmware on some watched not 4.1.2

  • over 1 year ago in reply to _psx_

    I tried this with current SDK set to 4.2.1 and device identified set to 4.1.7.  When running the app in the simulator, the app seems OK but for Fenix 7 series the bit maps are messed up when loaded.  I noticed that VS Code was building with SDK 4.2.1.  I guess I can't force it to use 4.1.7.??  Is the export prg going to be OK?

  • over 1 year ago in reply to trudelta

    I don't use vc do can't help, I've forced eclipse to build using any sdk.

  • over 1 year ago in reply to _psx_

    A Fenix 6 PRO user reported that the app stopped displaying body battery when I upgraded to SDK 4.2.1.  Supposedly the Fenix 6 PRO is not affected.  I tried building with SDK 4.2.1 but with affected devices set to 4.1.7. (But I am using VIsual Studio Code) , it did not solve the problem on the Fenix 6 PRO.  Any ideas on what is happening?

  • over 1 year ago in reply to trudelta

    as I've mentioned,

    _psx_ said:
    I've updated f6/f7 sim devices and have built my wf with 4.2.2, and there is no any problem with bb on device (25.10/11.28)
  • over 1 year ago

    Anybody published their app (or tried it on their problematic devices) with 4.2.3 and see if BodyBattery is working again? Release notes doesn't mention it so I don't have hopes high that it does fix it.

  • over 1 year ago in reply to SylvainGa

    What device?  I have a sideload I built with 4.2.3 for a test watchface where I can display any native complication.

    It also handles the glace for the configured complication.

    With BodyBattery, I subscribe and see the value, and if I press it, I see the glance, and the values match.