Help

Support

We read everything that comes in, and bug reports with a log attached get read first.

Email

For bugs, billing questions, account problems and anything else:
nativeworksapp@gmail.com

Please include your device model, your Android version, the app version from Settings → About, and what you were doing when it went wrong.

Service status

Sign-in, build permits, signing and the managed AI budget all depend on the Pocket Studio API. Editing, the terminal and Git do not.

Checking API…

Before you email

These cover most of what comes in.

A build failed and I don't know why

Open the Build workspace and read the output from the top — the first error is the real one, and everything after it is usually noise. The log from your last build is kept, so you can scroll back to it after switching away.

If the failure mentions memory, out-of-memory, or the build stopped without an error, see the next item.

Builds stop partway, or the app closes during a build

This is almost always Android reclaiming memory. A large Gradle build is a big allocation, and the system will kill apps — including the one in front of you — to stay alive. The app has guards that try to abort a build cleanly before that happens.

What helps, in order of effect:

  • Close other apps before a large build, especially browsers and chat apps.
  • Lower the build's memory settings in Settings if you're on a device with less RAM.
  • Let the device cool down between long builds, and build while charging.
"Build requires a connection"

That's expected. Every build checks in with our server for a permit before it starts, on every tier — it's how the project stays sustainable as a paid app. Editing, the terminal and Git all keep working offline.

If you are online and still see this, check the status indicator above, then email us.

Code completion isn't working

Completion comes from a real language server that installs on first use — check that the download finished, and give it a moment to index after opening a project. Kotlin resolution across your dependencies improves markedly after the project has been built once, because that's when the classpath becomes known.

The device gets hot and the battery drains

Compiling is heavy, sustained work in a small thermal envelope. This is normal for long builds and is not a malfunction. Incremental builds are much lighter. Building while charging, on a cool device, gives the best results — and the benchmarks page exists partly because thermal state changes build times so much.

I want to cancel my subscription or get a refund

Subscriptions are sold and billed by Google Play, so both live there: open the Google Play app → your profile → Payments & subscriptions. Refunds follow Google Play's refund policy. If something went wrong on our side, email us and we'll help you sort it with Google.

Cancelling a subscription is separate from deleting your account — see below.

I want to delete my account and my data

In the app: Settings → Account → Delete account. Full details of what is removed, and the web route, are on the account deletion page. What we collect and why is in the privacy policy.