On mobile back button pressed

[ulysses3117]

Checks

• I have read and understand the bug report guidelines
• I checked for existing similar reports to avoid submitting a duplicate
• I verified the issue occurs in the latest beta release to avoid submitting an issue that has already been resolved

Problem description

Hello, the issue is with the Browser behaviour event "On mobile back button pressed". Nothing happens when using the back button. The only way to simulate this that I am aware of is to have a build on an android or iOS phone.

Upload a project

mobileBackButton.zip

Steps to reproduce

1. Change mobileBackButton.zip to mobileBackButton.cp3
2. I've added touchable sprites that you can press to move between layouts.
3. The functionality is also there to switch between layouts using the "On mobile back button pressed" trigger. This is where the issue lies. When I use my mobile back buttons nothing happens. This worked before with no issues.
4. You may need to export this to android to test or maybe you can simulate the mobile back buttons being pressed.

Observed result

When using an Android phone pressing the sprites to switch between layouts works fine. You can switch between layout 1 and 2. When using the mobile back button to switch between layouts nothing happens.

Expected result

The mobile back button should work the same as using the touch controls on the sprites to switch layout.

Affected platforms

Android, iOS

Affected browsers

No response

Last unaffected release

r476-4

First affected release

r487

Additional remarks

No response

Platform information

The only way I can replicate this is to have a build on a mobile device. I cannot replicate on a Construct 3 preview or remote preview but here is the platform info where I'm working from anyway:

Product: Construct 3 r487 (stable)
Browser: Edge 148.0.3967.83
Browser engine: Chromium
Context: browser
Operating system: Windows 10
Device type: desktop
Device pixel ratio: 1
Logical CPU cores: 16
Approx. device memory: 16 GB
User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/148.0.0.0 Safari/537.36 Edg/148.0.0.0
Language setting: en-US
Audio sample rate: 44100 Hz
Audio output channels: 2
Audio output interpretation: speakers
Renderer: WebGPU
Compatibility mode: no
Supports GPU profiling: yes
Major performance caveat: no
Maximum texture size: 16384
Adapter details: nvidia/turing
Adapter features: bgra8unorm-storage, clip-distances, core-features-and-limits, depth-clip-control, depth32float-stencil8, dual-source-blending, float32-blendable, float32-filterable, indirect-first-instance, primitive-index, rg11b10ufloat-renderable, shader-f16, subgroups, texture-component-swizzle, texture-compression-bc, texture-compression-bc-sliced-3d, texture-formats-tier1, texture-formats-tier2, timestamp-query

[ulysses3117]

This is only on Android apps, I shouldn't have included iOS as an affected platform.

[pixelectrongames]

I have the same issue after the update. @AshleyScirra @DiegoScirra

[AshleyScirra]

We haven't changed anything regarding this recently - I'd guess one of the Cordova updates in a recent release caused this to change, but I don't recall seeing anything in the changelogs, so it might be a Cordova bug.

It would help us resolve the issue more quickly if you could provide/confirm the following information:

• verify whether the issue reproduces on iOS in a web browser
• verify whether the issue reproduces on iOS with an iOS app export
• verify whether the issue reproduces on Android in a web browser
• verify whether the issue reproduces on Android with an Android app export
• in each case test all beta releases for the last unaffected/first affected release fields - these should be one release number apart

Each case uses a different implementation - it would be surprising if both Android and iOS broke at the same time as they work differently, so it looks like there may be some conflating of different systems or issues.

[fredriksthlm]

We haven't changed anything regarding this recently - I'd guess one of the Cordova updates in a recent release caused this to change, but I don't recall seeing anything in the changelogs, so it might be a Cordova bug.

It was a code change for back-button in latest cordova for Android, don't know if you need to amend anything for it to work again though

apache/cordova-android#1831