Simulator Start bug - "You're almost there!"

🧑‍💻 Technical Support
, ,
1

Hi Tech Support,

I recently made a topic requesting if there was a way to fork/branch my repo from a commit because I couldn’t get my simulator to start properly.

I dug deeper into the issue and I think I found a bug related to the simulator starting.

The issue is that I get this screen:

To view this experience on your Android device, please open in Google Chrome or your native browser
To view this experience on your Android device, please open in Google Chrome or your native browser858Ă—1448 56.5 KB

Since I wasn’t able to go back to a working commit, I created a new branch and copied a starter project file by file. My project at that point looked identical to a starter project, but when I saved and built and hit preview/refresh/etc I still got the “You’re almost there” screen in the simulator, even though the starter project which had an identical file/folder structure was able to start correctly.

I’ve tried starting the app from a different browser (Chrome, Firefox, Safari) as suggested, and have even done the whole clearing history and cache, logging back in and restarting but none of those seemed to solve anything.

I also noticed one of the sample projects I cloned, with no changes to the code itself started showing this page even when it was working moments before. Given everything I tried, I think its possibly an issue with something happening on your side but have no idea what.

Just wanted to report this since its been frustrating trying to figure out what could be wrong. If anyone has ideas on how it can be fixed I’d love to know what has worked.

Thank you,

1 Like
2

Can you land your changes and share your project with the support workspace so I can take a look?

3

Yes, the project is not in my workspace so I had the owner share it to support:

This other project, which should be code-wise identical to one of your sample projects should have also been shared with you as well:

4

Hi @GeorgeButler , have you been able to get any more insight into this?

Seems the simulator still doesn’t work for us. I’ve cleared by cookies and restarted the laptop and it still doesn’t work. I was hoping your team would have looked into it or that maybe even the situation would heal on its own.

I posed my question more like a bug report, but actually our team will actually need support to get this working properly, as the first project will be a public project and is not just my hobby project I’m here to play around with. It really slows down development that we can’t get the simulator working.

I also I want to reiterate, the second project I shared is identical code-wise to one of your sample projects, you can check line by line, they are identical, yet the simulator is still not working for it.

One more detail if it helps you out. We’re all working from MacOS, using Chrome but have tried with other browsers as well (Safari, Firefox).

I’ll just re-post the same links again to be super clear.

Project we would like for the simulator to work:

Test project I used to see what’s wrong, but simulator is still not working (copy of place-ground, exactly the same, line by line, as your sample project):

Your sample project (“three.js place ground”) that was copied from, identical line-by-line to the test project above:

Thanks again,

6

bumping this thread. I’m another dev on this same project and am experiencing the same simulator failure issue.

7

I’ve been looking into the cause of this issue and it looks like this is an issue with something related to the landing page. If you remove the landing page from your included modules do you still see the same issue?

8

Hi George, thanks for looking into the issue.

I tried removing the landing page( window.LandingPage.pipelineModule() ), but unfortunately all I got was a white screen instead of the “You’re almost there” (for both projects), and the background video never loaded.

Good news is, this got me questioning the sample code, so I tried modifying a few things and in the end I got it to work by wrapping a few lines of code in a setTimeout:

app.js → onxrloaded :

  setTimeout(() => {
    // Open the camera and start running the camera run loop.
    document.body.insertAdjacentHTML('beforeend', camerafeedHtml)
    XR8.run({canvas: document.getElementById('camerafeed'), allowedDevices: XR8.XrConfig.device().ANY})
  }, 2000)

You can see the change in the latest commit of “threejs-place-ground” clone project.

Given setTimeout is probably not the safest way to delay things, is there a onLoad function or the like somewhere I can use?