I'm experiencing a serious touch input issue when exporting a Construct 3 project to Android.
The problem is very simple to reproduce:
I have a very small test project with no gameplay logic involved.
I place my finger on the screen and keep it there continuously.
On any touch start is triggered correctly.
After approximately 3 seconds, Construct triggers On any touch end, even though the finger is still physically touching the screen.
Approximately 0.5 seconds later, another touch start is triggered.
This cycle repeats roughly every 3 seconds.
So the sequence looks approximately like this:
Touch start → ~3 seconds → Touch end → ~0.5 seconds → Touch start → ~3 seconds → Touch end...
The important point is that the finger is never lifted from the screen.
The exact same test works correctly in Preview. The problem only occurs in the Android export.
I have already tested this with a minimal project specifically created to isolate the problem, so it is not caused by my gameplay events or control logic.
I also tried using CSS such as:
html, body, canvas {
touch-action: none;
overscroll-behavior: none;
}
and this did not solve the problem.
I'm using the latest version of Construct 3.
This makes the standard Touch object effectively unusable for continuous controls in a platformer. For example, if the player holds a virtual left/right button, the character stops responding for approximately 0.5 seconds every few seconds because Construct reports that the touch has ended while the finger is still down.
This is not something I can solve by simply ignoring Touch End, because the gap before the next Touch Start is long enough to make the controls noticeably unresponsive.
Has anyone encountered this behavior? Is this a known Android/WebView issue or a Construct 3 bug? Is there a recommended workaround or another input method that can reliably detect a continuously held touch on Android?
I can provide the minimal test project if needed.