PLAWIEPrivacy

Support · release train

Let’s get Plawie moving.

Start with the route that matches your problem. Keep credentials, wallet material, private conversations, and unredacted logs out of public reports.

1. Start here

LAUNCH DAYOfficial links · 12 AugustInstall and release-note destinations will appear after final gates pass.
BUG REPORTSPrepare a redacted reportThe official reporting destination will be published on launch day.
DIAGNOSTICSCapture the exact failureKeep the screen, step, app version, Android version, and smallest safe log excerpt.
SECRETSKeep credentials privateNever include keys, wallet material, tokens, or personal conversations.

WebsiteStatic launch site; no account or email capture.

AndroidNative-first release train with channel-specific runtime delivery.

Google PlayListing and final policy acceptance in preparation.

2. Fresh setup and downloads

  1. Use a stable connection and keep Plawie in the foreground during the first setup attempt.
  2. Leave the official Gateway notification active while its progress is moving.
  3. If setup resumes, do not clear app data; successful dependency receipts are designed to prevent repeat downloads.
  4. Capture the visible step name, exact error text, app version, Android version, and device model if it fails.

Plawie downloads the official upstream Gateway and resolves optional mobile runtimes through the approved mechanism for the installation source. GitHub sideload builds can use signed release packs; a future Play build will use Play-delivered executable modules.

3. Gateway startup

Open the Gateway logs page and check the runtime owner, endpoint, health, pairing state, and most recent bounded error. PRoot should appear only if you explicitly selected the rollback route.

  • Do not repeatedly force-stop and relaunch during an active repair.
  • Do not publish a localhost token, provider key, wallet address you consider private, or full conversation log.
  • Prefer the in-app repair action that corresponds to the failed component instead of clearing all data.

4. Skills and dependencies

A skill card can be ready, require configuration, require a native dependency pack, or be blocked on Android. Open the card for its exact state before reinstalling anything.

  • Configure: add the provider key, account, endpoint, or other field requested by that skill.
  • Download: install the displayed signed pack and wait for its receipt/status refresh.
  • Blocked: read the Android compatibility reason; a desktop-only binary cannot be repaired by repeated downloads.

5. Wallet, bridge, or payment problem

Stop immediately if the chain, token, recipient, amount, or quote differs from what you expected. Reject the approval and obtain a fresh quote.

For a useful redacted report include the app version, selected source/destination chains, token symbols, wallet type, bridge provider, approximate time, and transaction hash if one was actually broadcast. Never include a private key, recovery phrase, raw signature request containing secrets, or device authentication material.

No one providing legitimate Plawie support needs your recovery phrase or private key.

6. Delete local data

The current public build does not create a central Plawie cloud account. To remove local Plawie data, use available in-app deletion controls first, then Android Settings → Apps → Plawie → Storage → Clear data, or uninstall the app.

Clearing data can permanently remove credentials, conversations, receipts, downloads, and an internal wallet unless you completed an appropriate reviewed backup/export. Data sent to a model provider must be managed with that provider. Public blockchain records cannot be erased by Plawie.

7. Report a problem safely

The official reporting destination will be published here on 12 August. Prepare a report containing:

  • Plawie version and installation source;
  • device model and Android version;
  • the screen, step, or skill involved;
  • expected behavior and actual behavior;
  • the smallest redacted log excerpt that contains the error;
  • whether the problem repeats after a normal app restart.

Before attaching a screenshot or log, remove API keys, auth headers, wallet secrets, localhost pairing tokens, email addresses, personal messages, exact location, and private media.