Skip to content

Community and support

Support is deliberately concentrated in one place: every question and answer lives in GitHub Issues, searchable and in the open, with nothing split between a forum, a chat server and a tracker.

Choose the right route

You need Use
A reproducible defect Bug report
A missing public capability Feature request
Help diagnosing a build Read Troubleshooting, then open a bug report with the requested evidence
A responsible security report Follow the private process in SECURITY.md
An example worth sharing Open an issue with the complete app file, assets, screenshot and tested ApkPy version

Search existing issues before opening a new one. A minimal reproduction is more useful than a screenshot of the final exception alone.

What a useful report contains

ApkPy version:
Python version:
Operating system:
Command that failed:
Previewer or Android:
Generated project rebuilt after the change: yes/no
Minimal writehere.py:
Full traceback or Logcat cause:
Expected result:
Actual result:

For Android-only failures, include the first FATAL EXCEPTION and its deepest Caused by section. Remove tokens, signing material, device identifiers and private endpoint data before posting.

Start from a maintained example

There is no separate starter-repository catalogue yet. Until repeated user demand justifies maintaining one, use these versioned sources:

More channels as the project grows

GitHub Discussions, a public chat server and independent starter repositories will open once recurring questions and maintainers make them worth keeping. Until then, every decision and the whole support history stay in Issues, searchable in one place.

ApkPy is open source. Pull requests are welcome beside reproducible reports, documentation corrections and complete example apps; see CONTRIBUTING.md, and Licence and project continuity for what the licence says.