FAQ
# FAQ
# General Questions
# Q: Why can't I load the extension from source?
A: Possible reasons:
- You did not select the source code's root directory. When importing the extension, make sure you select the root directory:
- You may be trying to load it in Firefox. The extension does not currently support Firefox; support is planned for the future.
# Q: Why isn't a script working, or why is there no console output?
A: Possible reasons:
- The page needs to be reloaded. Reload the page after enabling or disabling any script so that injection settings take effect.
- console.log may have been disabled. Check whether
Hook logis enabled. Console output depends on console.log working correctly. If the script is disabled, try enabling it:
- The website may use anti-hook techniques. Try enabling anti-hook detection. If this still does not work, contact me with an example (WeChat: I-0xsdeo).
- For pages accessed through the
file:// protocolorlocalhost, see Quick Start > Notes.
# Q: Why don't keywords or fixed values configured in the Hook section take effect?
A: Reload the page to load the new settings.
# Script Questions
# Q: What should I do if Bypass Debugger doesn't work?
A: See Bypass Debugger for a solution. Another, more direct approach is to use Firefox to ignore breakpoints.
# Q: What should I do if the redirect interception script doesn't work?
A: See Locating JavaScript Redirect Code.
# Q: What if I still can't open DevTools with F12 after enabling the anti-debugging scripts?
A: First, try enabling all of the following scripts:
If you still cannot open DevTools, identify which situation applies:
- Right-clicking the website displays a message that blocks right-clicking or opening DevTools with F12.
For example:
You can bypass this by opening DevTools through the browser menu. Here is an example in Chrome:
- The page redirects to another website.
See Locating JavaScript Redirect Code.
# Q: Why is nothing captured when I try to extract encryption parameters?
A: Possible reasons:
- console.log may have been disabled.
See Hook CryptoJS > FAQ.
Encryption or decryption has not been triggered.
The website may not use the corresponding encryption library (CryptoJS / JSEncrypt / SM-crypto).
# Q: How do I get the padding and cipher mode?
A: See Hook CryptoJS > How do I get the padding and cipher mode?.
# Q: Why can't I encrypt or decrypt using the captured parameters?
A: See Hook CryptoJS > Why can't I encrypt or decrypt?.
# Q: Why can't I extract Vue routes?
A: Possible reasons:
- The page does not use Vue.
- The page does not use Vue Router.
# Q: Why am I redirected to the login page after clearing navigation guards?
A: Try the following:
- Enable the
Clear Redirectsscript. - If redirects still occur, see Vue > Redirects still occur after clearing.
# Q: Why can't the React script retrieve routes?
A: This script is still in an early stage of development and may not retrieve all routes. If you encounter this issue, please contact me with an example (WeChat: I-0xsdeo).
# Technical Questions
# Q: How do I report a bug or request a feature?
A: Submit a report on GitHub Issues (opens new window), or contact me (WeChat: I-0xsdeo).