How to write a good issue report
While we're trying our best and trying to use our knowledge to assist with your problem with the Termux applications, Before you post, please read the following first:
- Search for existing issues
Before you begin posting your issue, Use the "Search" function to search for problems that someone had reported before. It may have been solved previously. One good example is the "Termux Google Play" issues. Checking pinned issues and searching GitHub issues is also a good idea. This is not mandatory, but this saves time and energy. We also advise you to do your own research into the problem.
- Do not ping for help
Do not ping somebody for help. Learn how to wait because not everyone will get your problem and might not be active in your time zone, we'd expect a reward :)
- Elaborate on your problem
If you're encountering a specific issue, try to explain it as thoroughly as possible. If you don't know the roots of your problem, try to post the steps of how and when the problem was caused.
- Send your error output
The chances are your problem might be solved immediately by sending your terminal transcript through a screenshot or by "Share Transcript" in the Termux context menu by holding and tapping more. We also recommend to post the logs printed by the faulty program. If you plan to send longer logs, use paste services such as pastebin or attach a log file.
- Use Correct Tags
Use correct tags for your problem so it would be easier to find and filter specific issues based on the given tags.
- Make your title clear
The chances of people willing to assist you would be higher if your title is clear and concise. not too long or too short. Avoid titles with such examples like: "pls help" or "somebody help me?" without using your actual issue as a title.
- Be patient
You may or may not get any responses immediately as you post a problem.
4 Replies
This was meant to be a frozen forum but if you're asking for help here. open a new forum and unnecessary messages will instantly be deleted.
Please react to ☑️ if you acknowledged 🙂
This has the wrong wording. They meant "topic" in both places of their reply.
I did not expect to have much stars with this lol
If down here, scroll up to see the post. Also remember to use Markdown code blocks...
It is the grave / backtick symbol (NOT the single quote key) three times on its own line before and after the code / output)
```
It should look like this when typing it out.
```