Under Review
over 1 year ago

FW 20.75+ has fixes to backgrounding for Fenix 6 devices.

Fenix 6 with background app watchface doesn't update

A user has reported my watchface doesn't work with his Fenix 6 but does with his Vivoactive 3. So, he's been helping me debug it a bit and it appears that after the background process (which does a webRequest) calls Background.exit(data), the app's onBackgroundData() method isn't called, until something else, like a smart notification, happens on the watch.

He sees the same behavior with both firmware 9.0 and 10.10 on the Fenix 6. I don't see this problem on the simulator and this is the first report I've received about it.

Horsetooth
  • over 3 years ago

    I have the same problem using datalover watch face on basic fenix6 software 16.70.  When will this get fixed as a full year has passed?

  • over 3 years ago in reply to Brad.ConnectIQ

    Apparently it's not high on the priority list of the fenix6 team as this bug is nearly one year old...

    Could you pressure the fenix6 team a bit to put it in one of their next sprints?

  • over 3 years ago

    hi,

    may be Something which can help for this issue,

    I have 2 version of a watchface,

    the first one does not update weather, the 2nd one does update.

    I use exactly the same code for the weather except this:

    on the first one I use:

    AsP("blabla", NAME); or AgS(NAME); those functions are if has :storage then use App.Storage else App.getApp().set/getProperty

    and on the one which works directly  App.Storage.set/getValue

    hope it will help.

  • over 3 years ago in reply to Makkas-CIQ

    Many thanks for your answer, I am aware about oneCall but the one I talked about is the current API so it is not a memory issue... Very odd...

  • over 3 years ago in reply to Shent-Aurkhan (SHN)

    Hey!
    No, at that time (around 7 months ago), I didn't investigate further and I did not change code. As I wrote, there were very few users who had problems. And I had no more reports (besides those who could be attributed to wrong usage of user).

    Somewhere in May of this year I had to change code, because OWM changed the response of their one call API. They've put additional data in response when using their "daily" data, which made the response size way too big and I got out of memory in watch face. The quick fix was to remove daily data I used for forecast, and this worked (and works) until now.
    In addition, when using daily data, I assume that the response sometimes gets too big, and it totally depends on the location of the user and the data available at this specific location. Also, if it works on F6Pro (I own this watch too), it does not mean it works in other models, and simulator might not be on spot (I don't trust simulator much).