# Getting help (/docs/start/getting-help)



Developer support runs through your **Appbrew point of contact**: the person or shared Slack channel you were given when your repo was provisioned. That channel is the right place for anything in these docs; there is no separate developer ticket system.

For **merchant dashboard questions** that aren't about code (editing themes, managing screens, store settings), use the merchant help center at [help.appbrew.com](https://help.appbrew.com) instead.

## Getting access [#getting-access]

Everything starts with your repo, and repos are provisioned by Appbrew. Nothing here is self-serve. Three steps:

1. **If you have a Shopify store** (your own, or your product's demo store), install the [Appbrew mobile app builder](https://apps.shopify.com/mobile-app-builder-appbrew) on it.
2. **Send Appbrew**: the store's `.myshopify.com` domain, and the GitHub usernames that need repo access.
3. **You receive**: an invite to your repo, ready to run, with the `.env` preconfigured for your store and registry access already committed. Partners without a store are set up against a shared demo store instead, so you can start with no Shopify account at all.

From there the [merchant quickstart](/docs/start/merchant-quickstart) or [partner quickstart](/docs/start/partner-quickstart) takes over.

## What to include in a report [#what-to-include-in-a-report]

A report Appbrew can act on immediately has five things:

1. **Repo and branch** you're on.
2. **The exact command** you ran, copy-pasted.
3. **The full error text** — the whole output as text, not a screenshot of the last line. The real error is often far above the final message.
4. **Platform**: iOS or Android, simulator or device, and your macOS/Xcode or Android Studio version if the failure is a native build.
5. **What changed** since it last worked — a dependency bump, a pulled branch, a new machine.

Before reporting a build failure, check [Troubleshooting](/docs/ship/troubleshooting). The common ones have known fixes.

## Problems that need Appbrew's side [#problems-that-need-appbrews-side]

Some things you cannot fix locally. Ask straight away for:

* **Registry 401s** — `pnpm install` failing against `npm.appbrew.tech` with a 401 means your repo's read-only token has been rotated (or was never added). Appbrew issues a fresh one; see [Registry access](/docs/ship/registry-access).
* **Access requests** — a repo you don't have yet, Appbrew dashboard access, or (for partners) access to the sample app repo. None of these are self-serve.
* **Release questions** — store submissions, build pipelines, and release timing are coordinated with Appbrew; see [App releases](/docs/ship/app-releases).
* **Enabling a partner integration** — after [publishing your package](/docs/ship/publishing-packages), Appbrew flips it on for merchant apps.

## What you can expect back [#what-you-can-expect-back]

State clearly what you need (a token, access, an answer, a fix) and whether you're blocked. Blocked-on-Appbrew items (tokens, access) are usually quick. Debugging help moves at the speed of the detail in your report.

<Callout type="info" title="No public support email">
  Reach Appbrew through the contact or Slack channel you were given. If you've
  lost the thread, whoever set up your repo access can reconnect you.
</Callout>