testflight-dev-deploy
v0.0.8
Published
Expo Config Plugin to deploy dev app via TestFlight
Downloads
724
Readme
testflight-dev-deploy
Deploy your expo dev client app via TestFlight to your dev devices.
Enable TestFlight for Expo Dev Client apps
Out of the box Expo dev client apps can't be distributed through TestFlight. This tool fixes that. This makes it oh so much easier for developers on your team to test your expo app on real devices. And if you use it in combination with dev-client-mac-tools you can use your TestFlight dev client builds to develop expo apps on macOS without needing Xcode or the Simulator.
As a result developers on your team will be able to develop and test your expo dev apps on macOS, iOS and iPad OS without ever installing or touching Xcode or the Simulator.
- expo development without Xcode
- much more lightweight, robust development setup
- focus on your app, not on the native build process
- easy on click updates or even automatic updates via TestFlight
How does it work?
Out of the box Expo dev client apps can't be distributed through TestFlight: React Natives developer tools use so called "non-public API" and Apple therefore will automatically reject a dev client app if you try to deploy it through their infrastructure.
This config plugin removes the usage of non-public API. Luckily for us the only place where it's used is to read some short cut keys that we don't really need on a device.
So a the end of the day all this actually does is replace a #if RCT_DEV
macro by a #if 0
at the top of react-native/React/Base/RCTKeyCommands.m
.
Usage
- install expo module
expo install testflight-dev-deploy
- add the plugin to the
app.json
orapp.config.ts
in the root of our expo app like this:
{
plugins: [["testflight-dev-deploy", { enabled: true }]]
}
- add a development build configuration to our
eas.json
:
{
"build": {
"development": {
"developmentClient": true,
"distribution": "store"
}
}
}
Now we can trigger a build:
eas build --profile development --platform ios --auto-submit