How to Report a Bug in bannedbook/fanqiang: GitHub Issues and Code References

To report a bug in bannedbook/fanqiang, open a new issue on the GitHub Issues page at https://github.com/bannedbook/fanqiang/issues with a descriptive title, environment details, and reproduction steps.

The bannedbook/fanqiang repository maintains a centralized feedback system for its collection of circumvention tools, tutorials, and Android applications. When you encounter broken links, script failures, or configuration errors, following the project's standardized reporting workflow ensures developers receive actionable diagnostics. This guide covers the primary GitHub Issues channel, Android-specific helper functions in BugReport.kt, and command-line automation methods.

GitHub Issues: The Primary Reporting Channel

The repository uses the standard GitHub Issues workflow as its central feedback mechanism. According to the source code analysis, the README.md at line 86 explicitly directs users to the issues page with the instruction: "如需反馈交流，请点我或加入翻墙电报群". This convention applies uniformly across all sub-projects, including ChromeGo, EdgeGo, and V2Ray tutorials.

Accessing the Issue Tracker

Navigate directly to https://github.com/bannedbook/fanqiang/issues to submit a new issue. The 自建V2ray服务器简明教程.md file at line 93 reinforces this workflow, stating "有问题可以发Issue交流" (if you have questions, you can post an Issue to communicate) for server configuration problems. All tutorial markdown files within the repository contain footers directing users to this same URL, ensuring consistent feedback routing.

Essential Components of a Bug Report

When reporting a bug in bannedbook/fanqiang, include these five elements to expedite resolution:

• Title – A concise summary (e.g., "ChromeGo package fails on macOS 10.15").
• Environment – Operating system, tool version, and relevant configuration files.
• Steps to reproduce – An ordered list showing exactly how to trigger the error.
• Expected vs. actual behavior – Clear description of what should happen versus what occurred.
• Logs and screenshots – Relevant console output or visual evidence of the failure.

Android-Specific Reporting via BugReport.kt

For the Android components of the project, the source code provides utility functions in fqnews2/app/src/main/java/com/nononsenseapps/feeder/util/BugReport.kt. These helpers streamline the reporting process by pre-populating device information and offering alternative channels.

Email Bug Reports

The emailBugReportIntent() function generates an email draft containing system diagnostics. Use this code snippet in your Android environment to launch the default mail client with a pre-filled bug body:

// Launch an email intent with pre-filled bug report body
val intent = com.nononsenseapps.feeder.util.emailBugReportIntent()
startActivity(intent)  // Opens the default mail application

GitLab Issue Tracker Integration

For issues specific to the Feeder Android app component, use the openGitlabIssues() function to redirect users to the external GitLab tracker:

// Open the Feeder GitLab issue list in a browser
val intent = com.nononsenseapps.feeder.util.openGitlabIssues()
startActivity(intent)

While the core bannedbook/fanqiang project prefers GitHub Issues, these Android utilities provide flexibility for developers who prefer email-based reporting or need to access the separate GitLab repository.

Command-Line and API Methods

For advanced users and automation scripts, you can access the reporting system without a graphical browser.

Open the issues page directly from Linux or macOS terminal:

# Open the issue page in the default browser

xdg-open https://github.com/bannedbook/fanqiang/issues

Create issues programmatically using the GitHub API (requires a personal access token):

# Create a new GitHub issue via the API

curl -X POST -H "Authorization: token <YOUR_TOKEN>" \
     -d '{"title":"Brief title","body":"Detailed description"}' \
     https://api.github.com/repos/bannedbook/fanqiang/issues

Note: The repository does not expose a custom API for issue creation; the standard GitHub API is the recommended programmatic approach.

Summary

• Primary channel: Submit all bug reports to https://github.com/bannedbook/fanqiang/issues as referenced in README.md (line 86) and all tutorial documentation.
• Required details: Include environment specifications, step-by-step reproduction instructions, and relevant logs or screenshots.
• Android alternatives: Use emailBugReportIntent() or openGitlabIssues() from BugReport.kt for email drafts or GitLab tracker access.
• Automation: Use standard GitHub API endpoints or browser commands to programmatically access the issue tracker.

Frequently Asked Questions

Where should I report bugs for specific tools like ChromeGo or EdgeGo?

Report all bugs for ChromeGo, EdgeGo, and other sub-projects to the main https://github.com/bannedbook/fanqiang/issues page. According to the source analysis, all tutorial markdown files in the repository contain standardized footers directing users to this central issue tracker, ensuring consolidated feedback management across all components.

Can I report bugs via email instead of GitHub Issues?

While GitHub Issues is the preferred channel, Android developers can use the emailBugReportIntent() function defined in BugReport.kt to generate pre-filled email drafts containing device information. However, for the core repository tools and documentation, the GitHub Issues page remains the primary and most visible reporting method.

What information should I include when reporting Android app crashes?

Include your Android OS version, device model, app version, and the exact steps that triggered the crash. If possible, capture logcat output. You can also utilize the emailBugReportIntent() helper to automatically attach system information to your report before sending it to the development team.

Is there a way to check if my bug has already been reported before opening a new issue?

Yes, visit https://github.com/bannedbook/fanqiang/issues and use the search functionality to filter existing issues by keywords related to your problem. The repository maintains a public issue history, allowing you to identify duplicate reports or find existing workarounds before submitting new tickets.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}