Skip to content
Superapp
Esc
↑↓navigate↵open⌘Jpreview
On this page

Collect diagnostics and contact support

Send enough evidence to reproduce an issue without exposing credentials.

A useful support report lets someone reproduce the problem and identify the failing version without asking you to repeat the entire story.

Include these details

  • Your Superapp account email and project name.
  • Whether you are using Superapp Web or Mac.
  • The exact steps from a clean starting state to the failure.
  • What you expected and what happened instead.
  • The first exact error plus a screenshot or short recording when useful.
  • Device model, OS version, and whether Simulator, device, or TestFlight is affected.
  • The last time or project version known to work.

Remove sensitive information

Redact passwords, API secrets, private keys, signing certificates, recovery codes, service-role keys, access tokens, and personal customer data. A bundle identifier, non-secret error message, or Stripe receipt ID is normally enough to locate the relevant system without sharing credentials.

Make the scope obvious

One version or feature fails

Project-specific

Include the last change, affected files or screen, and a reliable reproduction path.

Several projects fail

Platform or account

Include the time, connection state, account status, and whether another device works.

Email support@superappp.com. If the issue concerns an external tool that edited a Mac project, include a summary of its changed files and configuration values.