# Known issues

What does not work yet, and what to do instead. This is the honest list for version 0.1. Nothing here is hidden from you at purchase time.

## Not built yet

| What | What to do instead |
|---|---|
| **Email sign-in for outside testers without a domain.** With no domain, sign-in codes come from Supabase's built-in sender, which only reaches members of your Supabase organization, a few an hour. Apps also have no email address of their own. | Try apps yourself without a domain. Before inviting testers who sign in by email, add a domain to Cloudflare and set up [Resend](vendors/resend.md). See [presets](presets.md#a-domain-is-optional). |
| **"Beta to my phone" preset and an Android preview build.** | Use **Ship to testers**: it builds for TestFlight and Google Play internal testing. Planned, no date yet. |
| **Integration switches** (turning individual vendors on or off per app). | An app uses the vendors its spec asks for. Leave a vendor's key unset to keep it off. Planned, no date yet. |
| **Apps without a backend.** | Every app gets a Supabase backend, even a simple one. Planned, no date yet. |
| **A license revocation check in the console.** | Nothing to do. Your install keeps working. |

## Things that work differently from what you might expect

- **A failed Quality Gate is reported, but it is not fixed for you.** The automatic repair step is switched off in the release you buy. When the gate fails, the run says so and shows why; fix it with a new run or by editing the app's repository.
- **A resumed run may count some Claude spend twice.** After a run pauses at your spend cap and you resume it, the figure on the run page can be higher than what Anthropic billed. Your Anthropic console is the real number, and your monthly limit there is the real backstop.
- **The cost figures in the guide are estimates.** They have not yet been measured on customer runs. See [costs](costs.md).
- **Store accounts take time.** Apple, Google Play and Twilio approvals take days or weeks, and no tool can speed them up. See [presets](presets.md).

## The first install on a fresh account

Starwisp has been tested end to end on its maker's own setup and by a dry run of the installer, but a first install in a brand-new organization is the one thing you may hit before we do. If the installer stops, it prints the reason, the fix, and a link, and running it again resumes where it stopped. If it still fails, send the output (never your keys) to [support](support.md).

## Report something

Use the diagnostics download in [support](support.md), which holds no key values, and write to the support address there.