Nw.js: binary protected js doesn't work when back or reload the page

Created on 19 Aug 2016 · 9Comments · Source: nwjs/nw.js

Hi everyone!

I have a problem with nw.Window.get().evalNWBin function, when the page loads for first time, my code works well, but when use window.history.back() or return to previous page, doesn't load again the protected binary....anyone can help me?

Thnx!!

bug triaged

Source

aarondiazr

Most helpful comment

i had figured out that it doesn't work then dev tools are open - once you close them - it works again

Asp3ctus on 16 Nov 2017

❤1 👍1

All 9 comments

I can confirm this issue.

ghostoy on 24 Aug 2016

this problem happens in LTS v0.14.7 too, nwjs-sdk-v0.14.7-win-ia32

XiaohuChen on 1 Mar 2017

when I rebuild the snapshot, it works well for one or two times when I reload the page, and the problem happens again

XiaohuChen on 1 Mar 2017

for me it also sometimes works some times not, like a lotery - the same snapshot, just restart the app, some times works sometime not

Asp3ctus on 6 Mar 2017

Has there been any movement on this? I can reproduce this issue

window v0.26.0 32bit and 64bit

refresh or history.back() , doesn't load again the protected binary

malacca on 10 Nov 2017

i had figured out that it doesn't work then dev tools are open - once you close them - it works again

Asp3ctus on 16 Nov 2017

❤1 👍1

@Asp3ctus THANK YOU!

I spent hours. Probably 5 or so. Debugging this. I closed Dev Tools. Reload app. SUCCESS!!!!

Crazy. This should be in

TxAg12 on 20 Mar 2018

I spent hours too. This is ridiculous. There is nothing more frustrating than poking around in the dark. Distilling an app down to the most simple <html></html>, and having the most simple index.js of console.log('asdf'); document.write('plz'), and opening dev tools, running nw.Window.get().evalNWBin( null, 'bins/index1234.bin' ), and if you change the file name, it fails, so you know it's opening hte bin, BUT NOTHING HAPPENS.

Put a comment saying DEV TOOLS CANNOT BE OPEN, seriously.