Acknowledged
CIQQA-4625

Wallet PIN blocked by activity screen

To reproduce:

 * Have a card set up in wallet with the PIN request set to ask when trying to spend not when first putting on the watch

 * Go to start an activity (e.g. Run) and leave it on the Acquiring GPS/Ready page

* Hold down the Light button and navigate to Wallet

* The PIN entry is blocked from being used until the activity page beneath has been left

  • I will report this to the product team, though  's suggestion to go through product support is the best option. They have an entire system in place to track external bug reports, and escalate them according to the severity and number of reports that are received.

  • I was able to reproduce this behavior as well. The issue appears to occur when touch is disabled during activities. When the Wallet PIN screen opens, the activity screen is still intercepting touch input, making it seem as though the PIN keypad is blocked. The workaround is to enter the PIN using the watch buttons, or temporarily enable Touch during Activity before opening Wallet. This feels more like a UX issue than a hardware problem, because there is no indication that button input is required. Garmin should either allow touch input on the Wallet PIN screen regardless of activity touch settings or display a clear prompt explaining that the PIN must be entered with the buttons.

  • Well if it was only about feedback then the situation would be 10 times better than now... They don't want to hear about bugs either

  • Thank you for your help. As a developer myself it is always disappointing when companies aren’t interested in user feedback…

  • There's no real way here. You can do the following things:

    1. user forum:  Forerunner 965 Sometimes other users can help. Garmin employees rarely read it though

    2. Garmin Customer Support: https://support.garmin.com/en-US/ This is the official place I think. The chat is a bit of a gamble though, depending on which representative you fall, you might get real help or it can be totally useless (in that case try a few minutes later again and again until you're connected to another person) OR you might write an email (which option is only available when Chat isn't) in which case you still have the earlier problem, but then at least you might get an email getting back to you if it's relevant (like they think they fixed the bug you you reported)