Black screen when exporting to Chrome Web Store

Report Construct 2 bugs here.

Post » Tue Aug 11, 2015 6:39 pm

Hopefully in the future I can figure out some sort of fix for this.
B
10
S
3
Posts: 109
Reputation: 1,080

Post » Fri Aug 14, 2015 12:42 pm

i get the same issue when i export my game app to the chrome web store and i cant find a single work around for it every time i try just a black screen
B
32
S
7
Posts: 24
Reputation: 1,570

Post » Fri Aug 14, 2015 1:49 pm

TMsimonW Sorry to hear that. Hopefully a good solution arises somehow in the future. Chrome web store is not my main area of publishing, however it would be nice as I do use a chromebook a lot for studying stuff.
B
10
S
3
Posts: 109
Reputation: 1,080

Post » Mon Aug 17, 2015 1:29 pm

As far as I can see the problem is specific to asm.js physics. If I set the .capx in this thread to use box2dweb physics, it works fine as a packaged app when tested from chrome://extensions. If anyone has any issues with the Chrome Web Store when not using asm.js physics, please file a separate bug report for that.
Scirra Founder
B
395
S
232
G
88
Posts: 24,368
Reputation: 193,746

Post » Mon Aug 17, 2015 1:36 pm

Ashley could you please be more specific on: "it works fine as a packaged app when tested from chrome://extensions." because I am just exporting from construct 2 selecting the chrome webstore option then clicking the index.html file this still brings up a black screen under box2dweb physics.
B
10
S
3
Posts: 109
Reputation: 1,080

Post » Mon Aug 17, 2015 2:09 pm

@SomeT - running from disk like that has never been supported - if it says file:/// in the address bar then it will never work, because browser security around local files prevents the game loading. You need to visit chrome://extensions and use the "Load unpacked extension" option. This is all documented by Google.
Scirra Founder
B
395
S
232
G
88
Posts: 24,368
Reputation: 193,746

Post » Mon Aug 17, 2015 2:49 pm

Ok many thanks.
B
10
S
3
Posts: 109
Reputation: 1,080

Post » Thu Aug 20, 2015 11:40 am

@Ashley Have you had a chance to file a bug against asm.js regarding this?
B
75
S
28
G
32
Posts: 480
Reputation: 19,711

Post » Thu Aug 20, 2015 1:26 pm

@Eisenhans - not yet, it needs more investigation. It's not yet clear whether asm.js inserts eval() calls or if the box2d port of the codebase does, or if asm.js' use of eval() is optional and was enabled for the build. Another solution could be to file a bug with the Chrome Web Store to allow eval() support in some cases, although I guess their main motivation is to improve security.
Scirra Founder
B
395
S
232
G
88
Posts: 24,368
Reputation: 193,746

Post » Thu Aug 20, 2015 2:44 pm

I got mine working by doing what you said, box2dweb and running chrome in developer mode etc... so thanks for that.
B
10
S
3
Posts: 109
Reputation: 1,080

PreviousNext

Return to Bugs

Who is online

Users browsing this forum: No registered users and 0 guests