Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

binary protected js doesn't work when back or reload the page #5225

Open
aarondiazr opened this issue Aug 19, 2016 · 9 comments
Open

binary protected js doesn't work when back or reload the page #5225

aarondiazr opened this issue Aug 19, 2016 · 9 comments
Assignees
@rogerwang
Labels
bug triaged

Comments

@aarondiazr
Copy link

aarondiazr commented Aug 19, 2016 •
edited

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!!
@aarondiazr aarondiazr changed the title binary protected js doesn't work when back or reload binary protected js doesn't work when back or reload the page Aug 19, 2016
@ghostoy ghostoy added the bug label Aug 24, 2016
@ghostoy
Copy link
Member

ghostoy commented Aug 24, 2016

I can confirm this issue.

@XiaohuChen
Copy link

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

@XiaohuChen
Copy link

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

@Asp3ctus
Copy link

Asp3ctus commented Mar 6, 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

@rogerwang rogerwang self-assigned this Mar 7, 2017
@malacca
Copy link

malacca commented Nov 10, 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

@Asp3ctus
Copy link

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

@TxAg12
Copy link

TxAg12 commented Mar 20, 2018 •
edited

@Asp3ctus THANK YOU!

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

Crazy. This should be in <h1 at the top of the protect code documentation.

@danschumann
Copy link

danschumann commented May 25, 2018 •
edited

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.

@sebadorn
Copy link

The issue with the open DevTools seems to be fixed. I tried it with NW.js 0.34.5 and 0.35.2 on macOS and it worked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rogerwang rogerwang

Labels
bug triaged
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
10 participants
@rogerwang @Asp3ctus @ghostoy @sebadorn @danschumann @aarondiazr @XiaohuChen @malacca @Christywl @TxAg12