Troubleshooting
Many common errors produced while using the State Tool can be resolved by either pushing your local changes to the Platform or pulling down changes from the Platform to your local machine.
- To push the local settings of your activated project to the Platform run
state push. - To pull changes in the Platform to your activated project run
state pull.
Issues with "lagging” or “hanging” projects may be resolved by closing your command line and re-opening and activating your project using the state use <orgname>/<projectname> command, or opening a new shell by running state shell <orgname>/<projectname>.
State Tool issues
If you encounter errors when using the State Tool, please reach out to our support team at support@activestate.com. The more information you can provide them with, the sooner your issue can be reproduced and resolved. Please provide the following information, where possible:
- A short summary of the issue
- Step steps to reproduce
- Expected result
- Actual result
- Logs (if relevant)
The State Tool logs are stored in the following locations by default:
- Windows:
C:\Users\<User>\AppData\Roaming\activestate\cli-unstable\log.txt - Linux:
~/.config/activestate/cli-unstable/log.txt - macOS:
~/Library/Application Support/activestate/cli-unstable\log.txt
More Troubleshooting
📄️ Git project mismatch warning
A "Git project mismatch" warning occurs when the project field in your activestate.yaml does not match the project you are activating. The most common cause of this warning is when activating a forked project where the original project has an associated git repository with an activestate.yaml in it.
📄️ Network Configurations
Problem Description
📄️ Uninstall
If the State Tool does not uninstall from your system after running the standard uninstall command state clean uninstall, try the following: