Back button or Ui.popView() problem on Forerunner 230?

We're having a problem with our app behaving strangely on the Forerunner 230 (firmware 3.11) when the Back button is hit.

We have a main view, then show a second view with Ui.pushView(). In that second view's delegate we have:

function onBack() {
Ui.popView(Ui.SLIDE_UP);
return true;
}

Rather than removing the second view and reshowing the first view, as we see on other watches, the app seems to restart. However we don't get an crash logs, and what we think is actually happening is that both the second view and and first view are being popped.

Perhaps the firmware is doing a popView in response to the back button even though we are returning true to indicate that we're handling the event??

Or it may be that the firmware is popping the first view in response to our popView call even though the second view is visible on top??

Nikeow over 9 years ago

Most likely related to the same issue I was seeing on the 630. Check out my post on the 630 start Key

mappicus over 9 years ago

Most likely related to the same issue I was seeing on the 630. Check out my post on the 630 start Key

Are you referring to the question of the 630 sending KEY_START rather than KEY_ENTER? I tend to think it's a different issue because in my case the Back event handler is definitely being called, but the firmware seems to be other things in response to the Back key.

jim_m_58 over 9 years ago

Does it sound something like this problem and involve session.start(), session.stop(), etc?

https://forums.garmin.com/showthread.php?236436

I've seen this on the 230.

mappicus over 9 years ago

Does it sound something like this problem and involve session.start(), session.stop(), etc?

https://forums.garmin.com/showthread.php?236436

I've seen this on the 230.

That's an interesting link thanks, as I have had users say that the first swipe/button press after starting (often this is the user swiping or pressing the up or down button to zoom the map on our dwMap app) is ignored. But I think my case is different as it happens well after that, it's after they've pressed the page up/down buttons a few times on the watch.

jim_m_58 over 9 years ago

That's an interesting link thanks, as I have had users say that the first swipe/button press after starting (often this is the user swiping or pressing the up or down button to zoom the map on our dwMap app) is ignored. But I think my case is different as it happens well after that, it's after they've pressed the page up/down buttons a few times on the watch.

In my app I see a lost key after a session.start(), and also after a session.stop().

So when I first start recording, I see it, and if I stop a recording to pause, I see it, and start the session after the pause and I see it. I don't see it when doing an addLap(), and not sure about session.save() or session.discard() (I'm done after those calls).

I have the same app on the vivoactive, and it loses swipes at the same times. Before this I just thought it was me doing a bad swipe, but looks like it's there too.

mappicus over 9 years ago

In my app I see a lost key after a session.start(), and also after a session.stop().

So when I first start recording, I see it, and if I stop a recording to pause, I see it, and start the session after the pause and I see it. I don't see it when doing an addLap(), and not sure about session.save() or session.discard() (I'm done after those calls).

I have the same app on the vivoactive, and it loses swipes at the same times. Before this I just thought it was me doing a bad swipe, but looks like it's there too.

Exactly yes--I thought I was just doing bad swipes too, but I see my Vivoactive does exactly as you say, not recognizing the tap or swipe after a start or a stop.

At least that's an easy issue to workaround for now. The problem on the FR 230 is a showstopper for us, we cannot get dwMap to work on it.

mappicus over 9 years ago

Garmin?

Would love to hear from the Garmin team on this: is it a firmware bug in the 230 (and probably the 235 and 630) or not?

Thanks!

Brandon.ConnectIQ over 9 years ago

So far, I haven't been able to reproduce this (in the sim or on the device), but I've isolated my testing to pushView() and popView(). I'll keep tinkering to try to reproduce and narrow down to a particular cause.

MoxyRoger over 9 years ago

Hi Brandon,

Can you give an update on the missed button press or missed swipe after an Activity Start or Stop?

That was reported 8 months ago and bumped a couple of times in the forum. It's a user interface problem that users see and can't be hidden by a code work around. Just curious why we've had numerous new releases but that problem never seems to make the cut to get fixed. It's disheartening to keep seeing talk of the same old bug especially if it's now showing up on new devices like the 230.

Is there more information that could be provided to help move this one along?

https://forums.garmin.com/showthread.php?236436-CIQBUG-Session-stop-causes-future-key-press-to-be-lost

Brandon.ConnectIQ over 9 years ago

Hi Roger,

I don't have much to update on this. The bug was reported in April, and I opened a case for it at that time. Perhaps we didn't have a full understand of just how much this has been impacting users, because it's been prioritized for a fix sometime next year. I assume it was considered lower priority since, unless I'm misunderstanding something, it's more of an inconvenience and just requires the end user to press a key twice.

I can raise this in our next planning meeting and see if we can't get this moved up in the schedule.