# Connect Expo and link your project

> Connect an Expo access token privately, select the correct account and link or create a project for your RNBlocks app.

Canonical: https://www.rnblocks.dev/docs/publishing/accounts/expo
Updated: 2026-10-01

The direct publishing build path uses an Expo access-token connection. Connect the account first, then choose the project for this app. GitHub is optional for this path.

## Before you start

- An Expo account, or permission to the Expo organization that should own the project.
- Your app open in Publish → Connections. On mobile, open Work first.

## Choose who owns the project

Section: https://www.rnblocks.dev/docs/publishing/accounts/expo#owner

Your Expo login can access a personal account and organizations. The selected account owns the project; a connection is permission to act, not a new project.

For team or client work, choose the intended organization. In Expo’s dashboard, open the account menu → Create Organization, enter its name and slug, and choose Create. Invite collaborators with suitable roles instead of sharing a personal password.

> **Already have the right account?**
> Keep it. You do not need another Expo organization for every app. Select the existing owner, then link this app’s own project.

### Figure: Choose an organization for shared Expo ownership

Expo’s Create an organization form asks for Organization name and Organization slug, with optional avatar and member invitations, followed by Create.

1. Use an organization when the project should belong to a team.
2. Choose a recognizable name and the intended organization slug.
3. Invite collaborators and grant the access they need.

Expo’s official organization setup example, with empty name and slug fields.

[Expo: Account types](https://docs.expo.dev/accounts/account-types/)

- [Expo personal and organization accounts](https://docs.expo.dev/accounts/account-types/)

## Connect your account

Section: https://www.rnblocks.dev/docs/publishing/accounts/expo#connect

1. **Open Connect Expo** — In the Expo section, choose Connect Expo, then Open Expo access tokens. Sign in or create your account on Expo.

2. **Create an appropriate token** — Expo personal tokens can act across accounts available to you. A robot token can use a limited role. Choose access appropriate for the project and keep the token private.

3. **Return to RNBlocks** — Enter it in Expo access token and choose Connect account. Wait for the connection result before selecting a project.

### Figure: Connect your publishing accounts

The Connections area contains separate Apple and Expo cards. The expanded Expo form links to Expo access tokens, explains personal and robot tokens, and has a private Expo access token field and Connect account button.

1. Open Connections in the publishing work area.
2. Choose the provider, then follow its account setup instructions.
3. Enter credentials only in the private form, never in the conversation.

Example: Connections with the Expo form open. Account and token fields are empty.

- [Expo access tokens](https://docs.expo.dev/accounts/programmatic-access/)

## Link an existing project

Section: https://www.rnblocks.dev/docs/publishing/accounts/expo#project

1. **Choose the connection and account** — Under Project for this app, select Expo connection, then Expo account. An organization’s project may be under a different account than your personal projects.

2. **Choose the app’s project** — Select Expo project and choose Link project. Use Load more projects when needed. Check the Linked project name afterward.

3. **Use an ID if needed** — Choose Enter a project ID instead, copy the ID from the project’s Expo settings, then choose Verify and link project. Typing an ID does not establish access until verification succeeds.

### Figure: Link the Expo project for this app

Project for this app shows an Expo connection, Expo account and Expo project selection, with Link project. The example project is @example-team/pocket-chef; no real account was linked.

1. Choose the saved Expo connection and the account that owns the project.
2. Select the project intended for this app. The connection and project are separate choices.
3. Use Link project after checking the owner and project. You can enter a project ID instead if needed.

The actual RNBlocks project controls with an illustrative Example team connection and Pocket Chef project.


## Confirm the project in Expo

Section: https://www.rnblocks.dev/docs/publishing/accounts/expo#expo-dashboard

Open the linked project in Expo and check its owner and name against RNBlocks Connections. Builds shown in that dashboard belong to that project. A saved token and an app’s selected project are separate parts of setup.

### Figure: Find the project and its owner in Expo

The Expo project Overview shows the project’s slug, ID and owner at the top. The sidebar includes Development builds, Builds, Submissions and project settings.

1. Check the account and project selected in Expo.
2. Use the project ID and owner to distinguish this project from other apps.
3. Return to RNBlocks to select and link the intended project.

Expo’s official StickerSmash tutorial example. Its account and project values are sample documentation values.

[Expo: Configure a development build](https://docs.expo.dev/tutorial/eas/configure-development-build/)


## If this app has no Expo project yet

Section: https://www.rnblocks.dev/docs/publishing/accounts/expo#new-project

Select the saved access-token connection and choose Use this account. Ask the publishing agent: Create an Expo project for this app in my selected account.

Review the proposed project and account before approving its creation. Once the project is linked, check its name in Connections. You can also create the project in Expo and return to link it.


## What about Sign in with Expo?

Section: https://www.rnblocks.dev/docs/publishing/accounts/expo#browser-signin

Other Expo connections contains Sign in with Expo. That browser sign-in connects Expo’s MCP tools. It cannot upload the direct release package, and its build tool requires a linked GitHub repository.

For the direct RNBlocks build path, use Connect Expo and an access token. A successful browser sign-in alone does not complete that setup.


## Connection or project missing?

Section: https://www.rnblocks.dev/docs/publishing/accounts/expo#troubleshooting

| What you see | What to do |
| --- | --- |
| No accessible accounts | Confirm that the token belongs to the correct user or robot and has access to the owning account. |
| No projects in this account | Choose the correct Expo account, create a project, or select Refresh projects after creating it elsewhere. |
| Reconnect required | Connect a valid token, then check the app’s project binding. |
| Changed project | Check the app identity and ask for a fresh build review. Old results still refer to the project used for those builds. |
| Disconnected in RNBlocks | Read the cleanup message. Revoke an access token in Expo when you also want to remove its provider access. |

> **Do not paste tokens into chat**
> Use only the Expo access token field in Connections. If a token was exposed, revoke it in Expo and create a replacement.


## Continue

- [Accounts and costs](https://www.rnblocks.dev/docs/publishing/accounts)
- [Release settings](https://www.rnblocks.dev/docs/publishing/release-settings)
- [Testing](https://www.rnblocks.dev/docs/publishing/testing)

## Official references

- [Expo access tokens](https://docs.expo.dev/accounts/programmatic-access/)
- [Expo personal and organization accounts](https://docs.expo.dev/accounts/account-types/)