Publishing , scanning qr code and opening experience in browser

🧑‍💻 Technical Support
1

Hopefully someone can help me with a publishing problem. I am doing a test using my trial period account, I have already completed the publishing process and I received the message that my experience was published correctly on my site, I enabled the publication in both staging and public, but I have not been able to test my experience correctly, when I scan the QR code of my experience I get a "experience not available" sign and when I enter the link of the experience directly in the browser, it asks me for the camera permissions of my smartphone (iphone 15 max) but it stays black (black browser window), does anyone know what’s happening?

2

Hi, welcome to the forums!

Are you using Safari on your iPhone? I would suggest trying Chrome to see if it works, as Safari is known to have issues when assigning the cooking required for previewing the dev build.

1 Like
3

The test i making is using Chrome. The black screen is within Chrome´s window…
thnks

4

Hmm, thinking more on it now it sounds like you might not have landed your changes before publishing, but even then you would at least see the default scene.

Could you share your project with the support workspace so I can test it with one of our test devices?

1 Like
5

I have repeated the publication process along with the landing the files step several times.
I have just shared the project…thnks

6

Hi @Andres_Delfin - thank you for your patience and raising this issue.

It looks like the “shortname destination” of your project was edited from the project dashboard, which is something that is supposed to be disabled for Studio Projects (this is a bug on our end, we will be removing the pencil icon that allows editing to prevent similar issues in the future).

Specifically, it looks like the name of your project was similar to “project1” and the shortlink destination was edited from the project dashboard to be similar to “project”. I have reverted the change so the url contains the 1 at the end again, effectively resolving the issue.

Note that if you want to update the URL, you will need to clone the project and assign a new name during the cloning flow.

Again, thanks for your patience and report. Please let us know if you have any further questions or issues.