Acknowledged
CIQQA-3823

Menu2InputDelegate.onSelect not triggered on touch devices in SDK 8.4.x

I recently upgraded to SDK 8.4.0 and then 8.4.1, and for the first time tested touch-based devices such as the Venu 4 and Vivoactive 6. On these devices, Menu2InputDelegate.onSelect no longer seems to be triggered when tapping a menu item.

I am using CustomMenu, not Menu2. On button-based devices such as the Fenix series, this still works as expected, even when interacting via touch rather than buttons.

Switching back to SDK 8.3.0 resolves the issue, which makes this look like a regression in SDK 8.4.x.

So far, I have only tested this in the simulator. I do not have access to real touch-based devices, so I am not sure whether this is a simulator-only issue or also affects physical devices.

the-ninth

  • The issue is still occurring in SDK 9.1.

  • I'm getting the exact same issue you describe with custommenu on X1, Venu2+ and Vivoactive5+. Works fine on other touch watches like forerunner and fenix. If I downgrade to 8.4.0 it still occurs.

  • in reply to flocsy🤠

    This is a very strange issue. I also tried the Menu2 example from the SDK, and that works. With my app, however, I can reproduce the problem on two different development environments, so it must be something in my code that triggers it.

    In the meantime, I discovered a workaround: a single tap does nothing at all, and a double-tap on any menu item except the last one also does nothing. The app only gets unstuck if I double-tap the last menu item. That double-tap pushes a new view, and after that view is popped again, the original menu behaves correctly.

    The last menu item is not functionally different from the others. I can reorder the menu items arbitrarily, and it is always whichever item ends up last that allows me to get the app unstuck.

  • it works for me in the simulator: SDK 8.4.1, venu441mm, Menu2InputDelegate, Menu2