Move, Rotate and scale disable on webXR / android

[3Dmoca]

move, rotation or scale doesn't work on webXR with AR.

This issue has only been detected on Chrome 139.0.7258.158 since the August 26 update. It works on Edge. I tested it on Chrome Beta and it works normally.

[ronpadz]

Confirmed also not working on Chrome 140.0.7339.52

Is working on Chrome Beta 141.0.7390.17 and Edge.

[StillOnMyWay]

Just confirming you're testing this with the mode set to webxr, and not the native mode (scene-viewer, quick-look)? https://modelviewer.dev/examples/augmentedreality/#ar

[3Dmoca]

Yes I confirm, and you can try it on the webXR example at https://modelviewer.dev/examples/augmentedreality/index.html#webXR

[StillOnMyWay]

Okay, I'm also on 140.0.7339.52, and I can't yet reproduce it unless I'm reading it wrong. Are you talking about manipulating the model with touch? Or via attributes/Javascript.

For the link you shared @3Dmoca , I was able to scale up and down, rotate and move the model on the example site in AR mode

[3Dmoca]

Yes, with touch on AR Android 15, same google version.

[ronpadz]

Android 16 on Pixel 6 Pro with September 5 update Google Play Services updated August 1

[vincentfretin]

I also have the issue since I restarted my Pixel 9 Pro because of a August or September Android update, but maybe it was also because of a Chrome update. There was no issue three weeks ago for me. Currently on Android 16; Pixel 9 Pro Build/BP3A.250905.014 Chrome 140.0.7339.123 Google Play Services for AR 1.50.251670093 When I touch the the model, the white rectangle shows sometimes briefly, but no move or rotate gesture is working anymore, with model-viewer 4.1.0. It is working with Chrome Canary 142.0.7420.0 although there is another issue with the rendering of the astronaut model but that's a separate issue.

[florian-forestier]

Hi, can confirm here on multiple device (Nothing Phone 3A Pro, Galaxy S24, Pixel 10)

Funny thing :

• On my Redmi Note 14, running Chrome 140.0.7339.123, GPS for AR 1.50.251670093 and Android 15, everything is fine.
• On my Nothing Phone 3A Pro, running Chrome 140.0.7339.123, GPS for AR 1.50.251670093 and Android 15, I have the same behaviour as @vincentfretin described.

The Redmi Note 14 is my usual phone, and I'm developing AR experiences on it every day. The Nothing Phone is a "test-phone" that I turned on to check the AR mode when my client said the AR is not working anymore on some phones. Maybe people who already started an AR Experience before 139.0.7258.158 have some cache or configuration that prevents the bug to occur ? Multiple people around me running AR experiences everyday are also not affected, but all phones with clean cache or fresh Chrome install are experiencing this issue.

On Chrome Devtools, nothing particular shows up on the Nothing Phone 3A Pro. The placement does not work at all (neither wall or floor), but no error log shown (even when listening to error event)

EDIT again : Same bug appears on Chrome Beta but not on Edge (latest version for both, specifically downloaded for the test).

EDIT of the Edit : The issue is on all examples using the modelviewer, including the examples at modelviewer.dev.

Final Edit : On Google Canary (142.0.7420.0), it works again on the Nothing Phone.

[samaneh-kazemi]

@3Dmoca I'm able to rotate and move the models in the examples below on S23, chrome 140.0.7339.123. Can you please add a video which has the exact repro steps? here is what I see https://modelviewer.dev/examples/augmentedreality/index.html#webXR:

https://github.com/user-attachments/assets/29e11e5f-c2f5-4839-9297-40f051bf84a4

[florian-forestier]

@samaneh-kazemi On a Nothing Phone 3A Pro, Android 15, Chrome 140.0.7339.123:

https://github.com/user-attachments/assets/b6faa136-5d83-4b87-88aa-9f03ade8e69d

[florian-forestier]

If it may be useful, on my Redmi Note 14 (GPS for AR 1.50.251670093 and Android 15) (yes, still doing some tests 😄) :

• Chrome 140.0.7339.123 (Usual browser) => Works as expected
• Chrome DEV 142.0.7405.2 (Fresh install) => Broken (same as video above)
• Chrome Canary 142.0.7420.0 (Fresh install) => Works as expected

So it sounds like this is not related to Google Play Services for AR, neither the Android version.

[vincentfretin]

On my Pixel 9 Pro

• I uninstalled Chrome, so this actually put back version 134.0.6998.135 => Works as expected
• I updated Chrome to version 140.0.7339.123 => Broken (same as @florian-forestier video)
• Chrome Canary 142.0.7420.0 (Fresh install) => Works as expected

[florian-forestier]

FYI on Chrome 140.0.7339.124 => Still have the bug.

The fact that my Redmi is not having the bug on an up-to-date Chrome build is funky: Maybe related to default flag values or default configuration?

EDIT : Also tried to downgrade model-viewer to 4.0.0 and 3.5.0 => the bug stays.

[3Dmoca]

I tried on a new Samsung A25, with identical settings and Chrome version 140.0.7339.123: webXr works correctly. On my S24, always doesn't work, but works on edge, chrome dev, chrome beta, samsung internet. Other people have tested on S23, Zenfold 4, S10 and encountered the same problem; it does not work.

@samaneh-kazemi : Video identical to Florian's. Thanks @florian-forestier

[Frank3K]

We are suffering the same issue with Chrome 140.0.7339.155 using WebXR. Rendering using scene-viewer does work.

Related Chromium issue: https://issues.chromium.org/issues/445949409.

[florian-forestier]

Hi, I'm taking a few time to troubleshooting it.

Function processInput (ARRenderer.ts#973) is a loop which checks notably for finger pressure on screen through a call to frame.getHitTestResultsForTransientInput.

On working browser, this function returns a XRTransientInputHitTestResult while my finger is on my screen. On non-working browser, the XRTransientInputHitTestResult appears only once, and then the result is empty.

Trying to push deeper but if someone have an idea (@samaneh-kazemi 😄), don't hesitate to continue the investigation.

[florian-forestier]

Hi everyone,

As you may see, I opened an issue on Chromium (link already sent before, but as a reminder: https://issues.chromium.org/u/1/issues/445949409). Do not hesitate to "+1" this issue (the button is on top-right) on Chromium side to get it more visible 😄. This bug is (very likely) in Chromium or Blink, so a patch can only come from their side.

[3Dmoca]

I didn't understand why, but the problem has disappeared for two days now, and Chrome is working normally again. Chrome version: 140.0.7339.207 I can't reproduce this issue anymore.

What about you?

[vincentfretin]

I still have the issue on Chrome 140.0.7339.156. I don't have it on Chrome Canary 142.0.7440.0.

[ronpadz]

Just retested and still experience issue on 140.0.7339.207

On Mon, Sep 29, 2025 at 6:30 AM Vincent Fretin @.***> wrote:

vincentfretin left a comment (google/model-viewer#5090) https://github.com/google/model-viewer/issues/5090#issuecomment-3346438974

I still have the issue on Chrome 140.0.7339.156. I don't have it on Chrome Canary 142.0.7440.0.

— Reply to this email directly, view it on GitHub https://github.com/google/model-viewer/issues/5090#issuecomment-3346438974, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHUKAD5TRZ7O3KGUB6AI6BD3VEJ33AVCNFSM6AAAAACFXH54VCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGNBWGQZTQOJXGQ . You are receiving this because you commented.Message ID: @.***>

-- Ron Padzensky, Founder and CEO Nvzn Augmented Reality Corp. Schedule a meeting with me https://calendar.app.google/Eq76rVmLd8rWCqhy7