My app unexpectedly ending during activity for my vivoactive 3

Hi,

I have a curious problem that i'm trying to resolve. This is actually a two part question and am wondering if any of the developers out there have found/resolved it. I have a Vivoactive 3 watch and thought it might be that there was some sort of false touchscreen read that was happening. Basically during my activity (a run) - my activity will end/exit without warning...seemingly randomly. For instance during a 10 mile run - for some reason it will end/exit at say mile 2.5...i'll then restart the app and it'll be fine until the end of my run. Today I went out for a 5 mile run - it happened after my about 3.5 miles, I restarted it and it happened again at just shy of a mile (.86). The thing is - it has worked just fine many, many times for all distances (11 milers, 4 milers, etc). What gives? I had thought that maybe my wet long sleeve shirt covering over it was the culprit...but i'm not so sure? Within my code - I return "true" for "onSwipe", "onMenu", and "onTap" functions in my delegate. I checked the logs on the phone and nothing is showing up that an error was encountered. So no log of what is going on (meaning it thinks it ended normally). Within my main view "onUpdate" - I do a try/catch block and then write out a system.println of the error message. It doesn't seem like this is being done (I was expecting an entry in one of the logs if an exception was encountered).

I HAVE noticed that during my app usage - I can always/still swipe right to exit out on my Vivoactive 3 with my finger (in spite of trapping an "onSwipe" action of true to disallow that)!!

Questions:
1) How to diagnose the issue correctly (and have other developers encountered this)?
2) If this is a false swipe positive on my watch - how to I lock it down better? How do I force it to NOT allow the right swipe exit? I thought that returning a true for "onSwipe" would do this...but clearly it doesn't as I can do it currently by my finger. Very annoying/frustrating.

I appreciate any/all help on this as i'm a bit stumped and not sure even how to diagnose it if no entries in a log are added, much less fix it. When it does exit like this - the activity does in fact save. In my one example today - I had two running activities during my run...one for 3.5 miles and another for that .86 mile. It is a strange one, folks. Please help if you have encountered this.

Thank you,
Matt

peterdedecker over 6 years ago

You'd better ask these kind of questions in the connect iq forum.

Error logs are stored on the device itself in the garmin/apps/logs folder.

I'm more into data fields than i am into watch apps but i think you want to handle the onBack delegate and prevent an exit there by returning true.

MJewett over 6 years ago

Thank you! So far, my fix is working. I've just added in a "onBack" function on three of my view delegates and am returning true on all of them. Seems to have done the trick. I'm new to creating apps, so am not as up on each user action to utilize in the delegate...so appreciate the help on this. :) I'll keep testing it, but until then consider this one closed.