SwiftUI Buttons and onMoveCommand Missing Presses

Question

Created Sep ’24

Replies 8

Boosts 5

Participants 7

In tvOS 18 the onMoveCommand is missing the first press after a view is loaded and every time the direction is changed. It also misses the first press on a button after a focus change. This appears to only impact the newer silver remote and not the older black remote or IR remotes.

With the code bellow press any direction 3 times and it will only log twice.

struct ButtonTest: View {
    var body: some View {
        VStack {
            Button {
                debugPrint("button 1")
            } label: {
                Text("Button 1")
            }
            Button {
                debugPrint("button 2")
            } label: {
                Text("Button 2")
            }

            Button {
                debugPrint("button 3")
            } label: {
                Text("Button 3")
            }

        }
        .onMoveCommand(perform: { direction in
            debugPrint("move \(direction)")
        })
        .padding()
    }
}

Answered by DTS Engineer in 805737022

The engineering teams would need to investigate this issue. I'd appreciate it if you could open a bug report, include the code and steps to reproduce the issue and post the FB number here once you do. Bug Reporting: How and Why? has tips on creating your bug report.

Boost

Answer 1

DTS Engineer OP

Apple

Sep ’24

Recommended

The engineering teams would need to investigate this issue. I'd appreciate it if you could open a bug report, include the code and steps to reproduce the issue and post the FB number here once you do. Bug Reporting: How and Why? has tips on creating your bug report.

0

Answer 2

respectTheCode2 OP

Sep ’24

I submitted a bug report (FB15272007) and requested code level support from the developer portal.

0

Answer 3

respectTheCode2 OP

Sep ’24

UIButtons do not appear to be impacted as well as pressesBegan but pressesEnded is inconsistent but not in a predictable way. It seems to be randomly missing presses.

0

Answer 4

IceRoad OP

Oct ’24

Having the same issue: onMoveCommand is not being called consistently on tvOS 18.0, often requiring 2 or 3 clicks on the remote to receive the callback. It's happening system-wide on other 3rd party apps as well.

0

Answer 5

smorlan OP

Oct ’24

Same issue here, onMoveCommand is not detected all the time. I need to use this modifier to keep a screen visible while the user in navigating in the view.. Any feedback?

1

Answer 6

archer56 OP

Oct ’24

I am also seeing the issue with onMovieCommand and it's easily replicable, where it seems to ignore the user input. But to add, I also see it on onTapGesture and onPlayPauseCommand also but to a lesser extent.

1

Answer 7

Justin_ OP

Nov ’24

Same issue, any updates about this issue?

Not only the onMoveCommand modifier, but also the select button can't respond the first press sometimes.

0

Answer 8

pilot_art_lis OP

1w

It looks like presses are missed only on tvOS 18+ (problem still exists in tvOS 18.2) with paired Apple TV Remote 2 and 3 gen. I tested in my app on tvOS 18.2 with paired Apple TV Remote 1 gen., and presses weren't missed; it reacted every time I tapped the right/left side of the remote.

0