Button state remains 1 for period after button is released

I'm currently using RemoteXY as a controller for a remote-controlled vehicle, which includes a function that should occur once when the user presses a Button element (it's a tank, button makes it fire). However, I've found that RemoteXY considers the button to still be pressed for long after I've released it in the app, resulting in code in loop running long after it should have stopped (around twelve loops worth when including a sound effect, as the code was until I found the workaround below).

I've found a way around this issue (checking if the state of the button in the last iteration of the loop was 1, ignoring it if so), but this is far from ideal as it probably forces me to play by the 'cooldown' of the button in RemoteXY, rather than anything I define in my own app.

Is this intentional or is this a bug? Or something else?