osa1 / dextrack Goto Github PK

I think sessions get invalid after 24 hours. We should add a debug log (it should print the time) when we got an invalid session. After a few days we should be able to look at the logs and figure out the exact lifetime of a session.

Once we know the session lifetime for sure, we can store the last login time, and when the time between the next request and the last session renewal is more than the lifetime we login again instead of trying to read the bg data.

We should show time left for the next temporal event in seconds when it's less than 60 seconds, otherwise we show it as minutes as we do now.

I think we should be able to use partial updates for this.

If we start using partial updates, maybe we can also show the second component of current time. We probably want to move the battery indicator to the left and use the space on the right for the second component.

When phone and watch go out of range, after connecting again, it seems like the next temporal event is not getting fired, and the app also doesn't schedule new temporal events.

As a result, we see "next event time" shown as negative number (i.e. we should've done a request but didn't) and we never update the bg levels again.

The workaround is to switch to a widget and then back to the watch face, which schedules a temporal event again.

We should find out which callbacks are called after a re-connection and schedule a temporal event there.