We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
https://oedx.github.io/2019/01/14/precise-positioning-cocos-online-error/
图片源自 Zoommy 在 Cocos-JS 的项目中,编译时往往采用 加密 + 压缩 的方式。最终 CocosCreator 编译出的代码文件都是无法直接阅读的,代码文件有 jsb_po
The text was updated successfully, but these errors were encountered:
现在构建后不是会生成一个“js backups (useful for debugging)”目录么?这里面就有行号一一对应的源代码,不需要解密
Sorry, something went wrong.
@jareguo 现在构建后不是会生成一个“js backups (useful for debugging)”目录么?这里面就有行号一一对应的源代码,不需要解密
有时候需要解源码的不是在构建的那台机器上,而是其他开发人员的设备,而大家又都有脚本加密密钥。这时候有一个解密工具就很方便了。
另外可以方便进行热更新验证,直接修改 project.js 然后加密就好了。不需要再次打包
干货,学习了
大神您好,解密之后也是混淆文件,我要怎么定位到原始代码的行列号
No branches or pull requests
https://oedx.github.io/2019/01/14/precise-positioning-cocos-online-error/
图片源自 Zoommy 在 Cocos-JS 的项目中,编译时往往采用 加密 + 压缩 的方式。最终 CocosCreator 编译出的代码文件都是无法直接阅读的,代码文件有 jsb_po
The text was updated successfully, but these errors were encountered: