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
Parents
  • over 3 years ago in reply to Makkas-CIQ

    hi , did you do something special to have it works? I had 2 reports of weather API not working on Fenix6, but 1 of them told me that he has your Alpha-Zulu which works great, but not on mine. I know there is nothing wrong on my side since it does work on mine (F6Pro) and on a VA4. It could be user missing but with 1 of them I did steps by steps (GPS etc)

Comment
  • over 3 years ago in reply to Makkas-CIQ

    hi , did you do something special to have it works? I had 2 reports of weather API not working on Fenix6, but 1 of them told me that he has your Alpha-Zulu which works great, but not on mine. I know there is nothing wrong on my side since it does work on mine (F6Pro) and on a VA4. It could be user missing but with 1 of them I did steps by steps (GPS etc)

Children
  • 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).