Help & support
Keep your integration
moving forward.
Start with a guide, check the setup requirements, or find an answer below.
Start with a component
Install the plugin, choose a feature, preview the code and finish the Android setup.
Understand an integration
Find SDK prerequisites, lifecycle hooks and the work your application or backend owns.
Licensing & generated code
Read about paid use, the no-trial policy and your rights to generated output.
Troubleshooting
Common questions
The tool-window button is not at the lower left.
A new default IDE layout places the button in the lower-left group and opens the panel at the bottom. An existing installation may restore a saved position. Use the IDE's Move to → Bottom action to reposition it.
The generator cannot find an Android module.
Open the Android Gradle project root and check the selected module's Android build configuration. You can still browse code and setup previews while module detection is unavailable.
Google SDK imports are unresolved after generation.
Follow the generated dependency guide, keep one owner for each library version, and sync Gradle. Projects using a version catalog or Groovy receive merge guidance rather than fully automated dependency integration.
Apply reports a conflict with an existing class.
Compare the existing file with the generated content. Keep your customized integration or choose another package and class name. Selecting another update mode does not migrate an existing component.
An update or review prompt does not appear.
Google Play controls update eligibility, review availability and quotas. Use the official testing setup for the selected API. A local debug installation is not proof of eligibility, and a review completion callback does not confirm that a dialog appeared.
Does the subscription component verify my customers' purchases?
It provides client-side Billing integration points. Your application and trusted backend must validate purchases, decide entitlements and acknowledge through a verified workflow. This is separate from the license for the IDE plugin.
How should I use rollback?
Save affected editor files and review the change plan. Apply and restoration register IDE Undo/Redo actions. Rollback checks every affected file and stops if you made later changes, preserving your customization. Use version control or backups for long-term recovery.
Where can I purchase or manage a license?
The commercial release and purchase links are being prepared. Licensing will use the relevant IDE and Marketplace flow. No trial is planned. Check the licensing overview for current release information.
When you need more help
A useful report starts
with the right details.
Contact Codetroupe at 294128852@qq.com. When reporting an issue, include:
- Plugin version and full IDE build number.
- The selected integration, language and update mode, if relevant.
- The action you took, what you expected and what happened.
- A short, sanitized error message or screenshot.
Remove passwords, access tokens, signing keys, service-account files, purchase tokens and confidential project content before sharing a report.
Read the data-use statement