Get the right help path for learners and managed rollouts.

Routing

The fastest route for help

• Public app users should start with the latest public app version and Google Play listing.
• Managed classrooms or cohorts should use the support route defined by their program owner.
• Custom deployments should begin with the team operating that infrastructure.
• Security reports should use the published disclosure path, not public issue threads.

Troubleshooting

Quick checks before escalating

• Confirm the device has network access and the current app release installed.
• Retry the challenge or feedback request after a short wait if provider capacity is limited.
• Check whether the issue affects one challenge, one device, or the entire rollout.
• Capture screenshots, error text, and exact reproduction steps before reporting.

Managed Rollouts

Support notes for schools, labs, and bootcamps

If your learners access InAppCode through an organized program, the first support point should usually be the deployment owner, instructor, or program administrator. They can determine whether the issue is local to one cohort, one environment, or a broader public-service problem.

Security

How to report a security issue responsibly

Use the published disclosure route in security.txt. Include the affected page or flow, reproduction steps, expected impact, and any supporting logs or screenshots you can safely share.

• Avoid public disclosure before the issue has been reviewed.
• Do not attempt destructive testing or access data you do not own.
• If a managed deployment is affected, notify that operator as well.

Common Questions

Support FAQ