Six Common HBuilderX and WeChat DevTools Failures and Their Fixes
These failures are common enough in Chinese university uni-app courses to warrant a dedicated troubleshooting post. For anyone teaching or maintaining a uni-app toolchain, the fixes are quick but the root causes—hardcoded paths, fragile caches, and version lock-in—are worth knowing before a classroom grinds to a halt.
Corrupted plugin caches or missing program files cause HBuilderX to report a plugin as perpetually running, with a clean reinstall as the only reliable fix. WeChat DevTools login failures that show success on the phone but stall on the desktop often stem from a version-specific compatibility bug, requiring a downgrade to an older stable release. When the run command prompts for a startup directory, selecting the root folder—not the executable—resolves the path detection.
Missing plugins, missing components, and dependency installations that hang beyond five minutes all point to a broken local environment that a full reinstall clears. HBuilderX becoming unresponsive after launch is typically caused by orphaned background processes that must be killed manually via Task Manager. The most specific failure occurs when a user has redirected the TEMP environment variable to a non-default drive: HBuilderX is hardcoded to read from C:\, so the mismatch breaks cli.js directory generation.
The TEMP variable issue reveals a hardcoded path assumption inside HBuilderX, which is fragile on any machine where users have moved temp directories to a different drive—a common practice on systems with small C partitions.
Several of these failures share the same blunt remedy: uninstall and reinstall. That pattern suggests the tooling lacks robust self-repair or cache-validation mechanisms, pushing the maintenance burden onto the user.
The WeChat DevTools login loop that requires a version downgrade points to a regression in newer releases, implying that the latest stable build is not always the safest choice for development.