Confirmed finish on maprung - not working?

[IanW15]

Due to various constraints we recently ran an event using 'confirmed finish'. It worked fine as described for phones but maprung didn't work as expected. When a Finish/Continue prompt appeared (on a false finish), scrolling and selecting 'Continue' simply returned the display to the original prompt and no subsequent controls were recorded. The only way out was to select 'Finish' at which point the run was terminated with the time of the false finish. I think all Garmin users experienced this if they had a false finish. I think there were 5 or 6.

I conducted some experiments to verify this and they behaved as above. Ignoring the prompt completely didn't work either, no future controls were recorded. I was using the latest version 1.8.7 on a Forerunner 245. I tried this on test events with both 'confirmed finish' set and not set, with the same outcome.

Has anyone else had experience of this? Have we misunderstood the procedure? (We don't intend to use it regularly!)
Ian

[Peter Effeney]

Ian

Sorry to hear of the issue.

I've just double checked the MapRunG code, and we don't actually send the Confirmed Finish flag to watches. That is, MapRunG should operate the same for a "normal" immediate finish and a "confirmed" finish event. The reason for this is that Garmin watches, in normal activity mode, require the user to confirm their finish anyway.... so you get "Confirmed Finish" on all events.

So, that's the theory! I'm baffled as to cause of what you are seeing.
Are you seeing the same behaviour for other events?
Maybe something has broken in an update (or for particular models of device)?

Could you please email [e-mail] with the .FIT file of an example please. (And any other relevant info)

Peter