Debug WeChat Public Account Locally with QQ Browser’s Tool
This guide explains how QQ Browser’s WeChat debugging tool lets developers run and test their server code locally without an external domain, by generating a public URL that forwards messages from the WeChat server to the local program.
When developing a WeChat public account, an external domain is normally required to receive push messages from the WeChat server, which makes development and debugging cumbersome.
QQ Browser now offers a WeChat public account debugging tool that allows developers to work on their local machines without needing an external IP or domain.
The tool displays received and sent message content and events, making development and issue location easier, and it can resend received WeChat packets to avoid frequent phone operations during debugging.
Principle
The debugging tool includes an internal server that monitors the developer’s locally running program and generates an external URL. By configuring this URL in the public account’s development settings, WeChat forwards messages to the tool, which then forwards them to the local program.
How to Use
(1) Start your local server program.
(2) Open QQ Browser, install “WeChat Debugging Tool” from the app center, and select “Server-side Debugging”.
(3) Enter the local server’s IP and port; the tool returns an external URL.
(4) Fill this URL into the public account’s backend developer configuration.
(5) Send a test message to the public account via WeChat.
For more details, visit the blog at blog.qqbrowser.cc .
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Java High-Performance Architecture
Sharing Java development articles and resources, including SSM architecture and the Spring ecosystem (Spring Boot, Spring Cloud, MyBatis, Dubbo, Docker), Zookeeper, Redis, architecture design, microservices, message queues, Git, etc.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.