Acknowledged
CIQQA-3248

Setting "Touch:Off" on Fenix 8, Forerunner 965 and FenixE fails to set isTouchScreen to false.

System.getDeviceSettings.isTouchScreen is returning true after touch is disabled in settings on Fenix 8, Forerunner 965 and FenixE

This behaviour is not showing up in the device simulator but is being widely reported on devices

https://forums.garmin.com/.../fw12-22-touchscreen-always...

https://forums.garmin.com/.../21-19-bug-touch-is-always...

https://forums.garmin.com/.../komoot-app-touchscreen-enable

It is a critical failure for my app which relies on this functionality to run on devices with both touch screen and 5-buttons.

It definitely works per the SDK documentation on Fenix 7 and many other 5-button touch screen devices.

Here is the failing code:

 var mySettings = System.getDeviceSettings(); 

 isTouchScreen = mySettings.isTouchScreen;

 //System.println("checkHybridTouchOff: hybrid, isTouchScreen:"+isTouchScreen);

 if (isTouchScreen){

  • And now I have developed, tested and uploaded a release of my app that circumvents this show stopper, but after 24 hours (and counting) the app store is still telling me : "This app has a version update pending. Changes will not be visible until the approval is complete. This process could take up to 2 hours." Grrrrr!

  • Yes, you are correct. Now that I have access to a user with a 965, I find that the touch screen does indeed remain active in my CIQ app despite it's being disabled in Settings.

    The issue is now being reported by 955 users of my app.

  • To be clear, the actual problem is that the touchscreen is in fact enabled for CIQ apps, even though the system "general use" touch setting is off, right?

    The fact that isTouchScreen is true is just a symptom of the problem. (But in fact it's not wrong - isTouchScreen accurately reflects the state of the touch screen.)

    That's my understanding anyway - I haven't encountered this bug myself, as I'm on FR955.