Ticket Created
over 3 years ago

CIQQA-447

FR 55 not remembering IQ Datafield

I have written a simple DataField App. It’s been published.

The issue I am seeing is the watch is not remembering that the field has been set when the activity has finished and the user returns to the Watchface. The next time the activity is selected the Datafield has returned to a standard Datafield. 

Have I missed some code or is this a bug with the 55? 

I am also seeing an “Edit Datafield Settings” message. But have no settings to adjust. Selecting Yes or No has no effect. Could this be part of the issue. 

TIMRETEX
Parents
  • over 3 years ago

    Hi Jim, thanks for getting back so quick. 

    No. Nothing at all. The App worked perfectly apart from that. The activity finishes and saves fine. All the time with the Datafield functioning as expected. 

Comment
  • over 3 years ago

    Hi Jim, thanks for getting back so quick. 

    No. Nothing at all. The App worked perfectly apart from that. The activity finishes and saves fine. All the time with the Datafield functioning as expected. 

Children
  • over 3 years ago in reply to TIMRETEX

    No. It’s still doing it. 

    If I select HITT and add my Datafield. Then return to the Watchface, it loses the Datafield when I return to HITT. 
    If I select Run and add my Datafield. Run Remembers it every time. And while it’s selected in Run, HITT will remember it all the time. 

    I’m also get the message “Edit DataField settings.” when I select the DataField. I don’t know where that option is set. There’s no mention in the API under SimpleDataField. 

  • over 3 years ago in reply to jim_m_58

    Looks like I misunderstood the hidden var type. Have set it to public var and seems to have fixed the issue.

    Strange that it worked fine otherwise, I would have expected nothing to work at all. 

  • over 3 years ago in reply to TIMRETEX

    What you're describing sound like what happens when a DF crashes.  This might be hard to find in the sim, but make sure that when you access things with "info" in compute() you always null check, as what's there/available can differ before you start recording, while recording, and after recording. See the API doc for getActivityInfo().