Javascript error while running a browser-desktop game

[Baris Ayaz]

Hello,

I'm getting the following errors when I try to start a "browser-desktop" generated game.

Application Cache Error event: Resource fetch failed (404) http://localhost/mygame/_resources
Uncaught TypeError: Cannot set property '__root' of undefined

The following command is used to build the project.

devkit release browser-desktop -u http://localhost/mygame/

The project is build with devkit v.2.1.1.

Running the same project in the simulator either as an native-ios app has no issues.

Any ideas what I'm missing to deploy a "browser-desktop" deployment?

Thx

[Collin Green]

Hi Baris,

I'd like to reproduce your error locally and fix it, but I haven't been able to yet.

What is the -u http://localhost/mygame for and/or what do you have set up there for resources?

I successfully made a browser-desktop build of the demoAnimation project with the following commands:

git clone g...@github.com:gameclosure/demoAnimations

cd demoAnimations

devkit install

devkit debug browser-desktop

Then I hosted it locally with this:

cd build/debug/browser-desktop

python -m SimpleHTTPServer

Then the demo works in my browser at localhost:8000

Do you have the same error if you do these steps with the demoAnimations project?

[Michael Boulet]

I also have the problem when doing a release build. Works fine with a debug build. I'm using devkit 3.1.3.

[Tom Geiger]

Hi, I am still experiencing this problem when I try to create a release build of the "Platformer" demo game.

Steps to reproduce:

1. Clone the repo:

git clone https://github.com/gameclosure/platformer.git

2. init devkit:
devkit install

3. make release build:

devkit release browser-desktop

4. Open index.html (served on local apache server) results in console error:

start-app failed TypeError: Cannot set property '__root' of undefined

    at buildApp (http://localhost/release/browser-desktop/game.html/modules/devkit-core/src/clientapi/index.js:1:2743)

    at startApp (http://localhost/release/browser-desktop/game.html/modules/devkit-core/src/clientapi/browser/launchClient.js:1:611)

    at queueStart (http://localhost/release/browser-desktop/game.html/modules/devkit-core/src/clientapi/browser/launchClient.js:1:308)

    at Object.$$devkit_browser_launchClient (http://localhost/release/browser-desktop/game.html/modules/devkit-core/src/clientapi/browser/launchClient.js:1:2048)

    at I (http://localhost/release/browser-desktop/browser-desktop.js:2:5069)

    at z (http://localhost/release/browser-desktop/browser-desktop.js:2:6670)

    at http://localhost/release/browser-desktop/browser-desktop.js:2:7349

    at Object.window.GC_LOADER.controller.pipeline.call (http://localhost/release/browser-desktop/game.html:185:11)

    at nextPhase (http://localhost/release/browser-desktop/game.html:49:29)

When creating a debug-build using "devkit debug browser-desktop" the game starts up fine.

Any ideas what's going wrong there?

[Tom Geiger]

It turned out that the "const" variables in the platformer demo's Application.js were causing the faulty build. After I changed each of them to var, the release build was working.