LONG Press Down button and pressing Back/LAP will exit app

https://forums.garmin.com/showthread.php?304883-Session-AddLap-Stops-activity-GPS-amp-other-funky-issues-w-auto-notification-of-LAP&p=681794#post681794

I deem this to be a regression to the above linked post. While some of it has been fixed (notably by removing the native lap screen) but I think there's another thing happening where the the native Garmin App (Runing or otherwise) would still come up/out.

test case.

1) Start CIQ App recording
2) long press DOWN button to get to widgets.
3) go to music widget. Advance playlist to next song
4) Press Back/LAP button (in hope to get back to the running app)

Expected behaviour
After pressing the back/lap button, CIQ app will return back to the running app

Actual Behaviour
After pressing the lap/back button. Running CIQ App will exit (data not saved) and user presented w/ the native Garmin Running App.

I have tested this happening on a few apps. My Own MyCustom RunFields app and the dwMap app (also tried GolfScoreCard)

Would appreciate some comments/feedback on this.
Until a fix is available - I guess I can/have to disable the app from going into the Widgets? (how does one do that actually? Remove out the On-Hide?)

Note : If I were to cycle the app back to the Watch Face (the default native Garmin Digital Watch face), press ENTER key, then it will go back to the APP w/o issues.

perhaps I am not doing the right thing and still catching the LAP button presses when its in the Widgets/Watch face screen? But even so, should it not revert me back to the Running CIQ app and not throw me to the native Garmin Running App?

Former Member over 9 years ago

Disabling exit to the native pages requires processing the "CLOCK_KEY" in the inputDelegate, and returning 'true'.

You won't get key presses when your app isn't active, so any Lap key processing you are doing is not related to this issue. I've reported this bug to the device team.

Nikeow over 9 years ago

Thanks Brandon. I've successfully used your suggestion and disabled for the KEY_CLOCK for the time being.
This is on an F3 - I am not sure if the same is true for the other watches.

Would you happen to know?

Former Member over 9 years ago

I'm really not sure. We would have to try out the particular sequence on the other devices. I would not be surprised if they all had the same behavior. VivoActive is the most likely to behave differently. FR920 can't exit to widgets, so it should be fine.