Community and support

Stuck? Before asking, the first stop is self-help; then, the people channels.

First stop (solves most cases)

1. FAQ — common questions in 1–2 sentences.
2. Troubleshooting — errors by symptom (compilation/runtime/render/build/platform).
3. Reference — the exact signature.

People channels

• Community discussion (forum/chat) — usage questions, patterns, feedback.
• GitHub issues — bugs and feature requests (with a minimal reproduction).
• Commercial channels (Sovis, the maintainer) — dedicated/commercial support, distinct from community support.

How to ask a good question

Always include:

• The CrossFly version and target platform (desktop/Android/iOS/Web).
• The DebugConsole.txt (or the relevant log) — exceptions in callbacks are funneled through Debug.handle.
• An MRE (minimal reproducible example) — the smallest screen/snippet that reproduces the problem.
• What you expected vs. what happened.

This speeds up the answer and avoids back-and-forth. Compilation errors after updating? It’s probably the 2026 modernization — check the fix table.

See also

• Changelog / What’s new · Roadmap · Contributing