1.1.0

Login to Expo account before ejecting the project if both user_name and password is provided.

1.0.0

• Remove expo cli eject method #13

0.10.2

Step description update.

0.10.1

• Updated step.yml to match sharing requirements.

0.10.0

Replaces the plain eject-method with bare as plain is not supported anymore with the expo-cli.

The difference is that a bare project is based on expo-template-bare-minimum and therefore includes unimodule support.

0.9.3

New features:

Run expo publish after eject?

Should the step run expo publish after eject?

In case of React Native project using Expo Kit library (any .js file imports expo),
expo publis command generates the:

• ./android/app/src/main/assets/shell-app-manifest.json
• ./android/app/src/main/assets/shell-app.bundle
• ./ios/bitriseexpokit/Supporting/shell-app-manifest.json
• ./ios/bitriseexpokit/Supporting/shell-app.bundle

files, which are required for the native builds.

React Native version to set in package.json

React Native version to set in package.json after the eject process.

Commits:

• [daaa787] Publish (#5)

0.9.2

• [b3ca09b] fix: fix some typos (#4)

0.9.1

• [4336a41] refactor: rename the step from Expo Detach to Expo Eject (#3)

0.9.0

Basics

This step uses the expo-cli to create Xcode and Android Studio projects for your app.

Eject Method

• If you use any Expo SDK you must to provide username and password for your Expo account.
  Because in this case, the expo-cli will use the expoKit eject method which needs an account.

• If your project does not import any Expo SDK then you should not use the username/password option.
  Because in this case, the expo-cli will use the plain eject method.