fix: resolve #1188 — 360加固之后 补丁下载成功合成成功 之后打开一直重启

[Nam0101]

Summary

fix: resolve #1188 — 360加固之后 补丁下载成功合成成功 之后打开一直重启

Problem

Severity: Low | File: .github/ISSUE_TEMPLATE.md

A large fraction of "patch merged but app won't start" reports stem from APK hardening, custom multi-dex loaders, or mismatched tinkerId. The current template appears to ask for tinker version, gradle version, SDK, and OS, but does not prompt the reporter to disclose whether they used a hardener or to attach the relevant Tinker.with(...).getLoadReporter() / tinker_server logs. Adding two checkbox-style questions makes triage instant and gives the reporter a chance to self-diagnose.

Solution

Add fields to the template:

Changes

• .github/ISSUE_TEMPLATE.md (modified)

Testing

• Existing tests pass
• Manual review completed
• No new warnings/errors introduced

---

Note: this change was drafted with AI assistance and reviewed locally before submission.

[tencent-adm]

Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}