Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to start WebXR AR session on S24 #1655

Open
simonedevit opened this issue May 20, 2024 · 12 comments
Open

Unable to start WebXR AR session on S24 #1655

simonedevit opened this issue May 20, 2024 · 12 comments
Assignees
Labels

Comments

@simonedevit
Copy link

SPECIFIC ISSUE ENCOUNTERED

I'm unable to start an AR session from a browser (Google Chrome/Samsung Internet Browser) on Samsung Galaxy S24.

VERSIONS USED

  • Device manufacturer, model, and O/S: Samsung Galaxy S24, SM-S921B/DS, Android 14 (One UI 6.1)
  • Google Play Services for AR (ARCore): 1.43.240930493
  • Google Play Services version: 24.16.16: 190408-629452829

STEPS TO REPRODUCE THE ISSUE

  1. Go to https://immersive-web.github.io/webxr-samples/immersive-ar-session.html
  2. Press on "START AR" button

WORKAROUNDS (IF ANY)

ADDITIONAL COMMENTS

Inspecting the device with Chrome Developer Tools, it seems an issue during the creation of XRSession due to not supported configuration.

Screenshot from 2024-05-20 19-18-31

Same test is working on a Samsung Galaxy S10 (Google Play Services version: 24.16.16: 190400-629452829).

@Ledenik
Copy link

Ledenik commented May 25, 2024

The same thing happens on my Galaxy A55

As far as I can tell, it's because Samsung/Google haven't certified the devices for ARCore yet. If you look at the list of supported devices, S24 and A55 are both missing.

@Ledenik
Copy link

Ledenik commented Jun 6, 2024

Just to post an update, because I'm want to get this to work on my A55. The list was updated and it now includes both of the devices I mentioned in the previous comment, but they're both missing the "Supports Depth API" in the last column and the demos still don't work. I don't know what this implies, but I'm a bit disappointed.

@devbridie devbridie self-assigned this Jun 11, 2024
@devbridie
Copy link
Member

Hey, looking into this - the S24 and A55 definitely do support Depth API but it seems there's a mistake on the device table.

Few questions about this:

  1. Do any ARCore apps work on the affected devices?
  2. Have you tried the samples on Chrome on the affected devices?

@Ledenik
Copy link

Ledenik commented Jun 11, 2024

Yes, to both.

I downloaded the Google Depth Lab app on my A55 and every sample works.
I tried the samples on Chrome, since it's practically the only browser that supports WebXR. I know there are others, but as far as I can tell, they're all based on Chromium.

I have the latest version of Chrome, I keep it updated, hoping it would work, but it never does. I get the same errors as shown in the first post.

@Ledenik
Copy link

Ledenik commented Jun 11, 2024

Some additional info, when I check the permissions on the WebXR samples website, it says the camera is turned off in the Android settings.

I double checked everything, and I have camera access enabled in the site settings in Chrome and in the Android settings.

@cedgraph
Copy link

Same issue on my S24
Tried with google library model-viewer

@krzys-h
Copy link

krzys-h commented Jul 19, 2024

Same issue on S22+. It seems like it tries to launch the session, but the AR view window never opens. Logcat suggests that ARCore is actually running underneath. Pressing the back button causes the Could not create a session because: Something went wrong initializing the session in the runtime and The specified session configuration is not supported message. This happens on every WebXR sample I tried, and definitely worked in the past (or at least I'm 99% sure it did, as I switched phones recently).

ARCore apps outside of the browser work fine.

@krzys-h
Copy link

krzys-h commented Jul 29, 2024

I did some digging around trying to downgrade versions, and figured out that this is actually an issue on the Chrome side, introduced in Chrome 121. I reported the issue on their tracker here: https://issuetracker.google.com/issues/356039079

As a workaround, you can downgrade Chrome to 120 and ARCore to 1.39 (the latest versions of ARCore are too new for the old version of Chrome)

@Ledenik
Copy link

Ledenik commented Aug 9, 2024

Good news. The issue has been fixed, but it's not available in the stable release yet. You have to install Chrome Dev. It will be available in the stable release on Sep 17.

@cedgraph
Copy link

Issue come back since Sept 5th, new version of chrome dev : Chrome Dev 130.0.6696.0, android 14, Samsung S24 SM-S921B
Crash reported on Chromium : https://issues.chromium.org/365299876 Crash report for webXr
test on chrome canary, idem

@krzys-h
Copy link

krzys-h commented Sep 28, 2024

On the current stable release, Chrome 129.0.6668.70, the issue is finally gone.

@Ledenik
Copy link

Ledenik commented Oct 1, 2024

On my A55 it doesn't work. On the stable release, it's the same as in the report, and on Chrome dev this happens:

webxr_chrome_dev2.mp4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants