Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Unite 2023 Registrations are now LIVE! We are thrilled to announce that Unite 2023 Registration is now live and open for all!
    Dismiss Notice
New Forum User Notice Unite 2023 Registrations are now LIVE!

Bug Unity Play site broken for some games - stuck at 0% after clicking play (Cross-origin bug)

Discussion in 'Editor & General Support' started by msyoung2012, Mar 26, 2021.

  1. msyoung2012

    msyoung2012

    Joined:
    Mar 20, 2014
    Posts:
    49
    Some games get stuck at 0% when you click the "play" button in Chrome. For example: https://play.unity.com/mg/other/very-slow-build-032421

    Checking the console reveals:

    Uncaught DOMException: Blocked a frame with origin "https://play.unity.com" from accessing a cross-origin frame.
    at https://play-static.unity.com/publi...oller.69ca682634efac49d862.bundle.js:1:376887
    react-dom.production.min.js:52

    Looks like a cross-origin mistake on the Unity Play team's side, maybe trying to serve some game information from one place and some from another? Got a few users experiencing this error - anything we can do to fix or is this just a Unity problem?
     
    msyoung2012, Mar 26, 2021
    #1

  2. xBelabz

    xBelabz

    Joined:
    Nov 9, 2015
    Posts:
    1
    Hi,

    Under the chrome settings, you should allow all cookies or keep the configs as I did by blocking the third-party cookies for more secure browsing on the web and allow third-party cookies for https://play.unity.com only. You can do it as you wish but you should allow the third-party cookies for unity to work properly.

    Screen Shot 2021-05-24 at 3.13.41 PM.png
     
    xBelabz, May 24, 2021
    #2

  3. johanepic

    johanepic

    Joined:
    Sep 21, 2021
    Posts:
    4
    Normally, scripts on different pages are allowed to access each other if and only if the pages they originate from share the same protocol, port number, and host. Above error message shows that you can't access an < iframe > with different origin using JavaScript/jQuery, it would be a huge security flaw if you could do it.

    window.postMessage() provides a controlled mechanism to securely circumvent this restriction.
     
    johanepic, Sep 21, 2021
    #3