The Taro Playground App is a cross-platform application developed using Taro, to help developers develop and debug Taro applications. It is initialized using taro react native template.
https://testflight.apple.com/join/RDFCp2yy
- taro:
@tarojs/cli@^3.2.0 - framework: 'react'
| Playground Version | Taro version | React Native version | branch |
|---|---|---|---|
| 1.1.2 | >= 3.2.0, < 3.3.10 | 0.64 | releases/rn-0.64+taro-3.3.9 |
| 1.2.0 ~ 1.3.9 | >= 3.3.10, < 3.4.2 | 0.66 | releases/rn-0.66+taro-3.4.2 |
| 1.4.0 ~ 1.4.8 | >= 3.4.2, < 3.5.0 | 0.67 | releases/rn-0.67+taro-3.4.10 |
| 1.6.0 ~ 1.6.5 | >= 3.5.0, < 3.5.6 | 0.68 | releases/rn-0.68+taro-3.5.5 |
| 1.7.0 ~ 1.7.4 | >=3.5.6, < 3.6.0 | 0.69 | releases/rn-0.69+taro-3.5.11 |
| 1.8.0 ~ 1.8.2 | >=3.5.6, < 4.0.0 | 0.70 | releases/rn-0.70+taro-3.6.18 |
| 1.11.0 ~ | >=4.0.8 | 0.73 | main |
install peerDependencies of
@tarojs/taro-rn@tarojs/components-rnand@tarojs/router-rn, it will also runpost-install. please modify and runupgradePeerdepsscript when you change taro version.run this script after the project is initialized.
yarn upgradePeerdeps
run this script when you add new react native library or update react native library version.
see pod-install for more information.
yarn podInstall
yarn ios
yarn android
yarn start
yarn start --reset-cache
- development process of taro react native
- github address of the taro project
- related articles of taro playground
yarn build:rn --platform ios
yarn build:rn --platform android
see publishing-to-app-store for details.
see signed-apk-android for details.
use github actions to build your apps. this template include basic github action config.
see .github/workflows for details.
we assemble debug and release product for both android and ios when you push or pull request on master branch by default. design your own pipeline by modify .github/workflows files.
see events-that-trigger-workflows
Modify the following configuration items for package and publish your app.
.github/workflows/assemble_ios_debug.yml .github/workflows/assemble_ios_release.yml
env:
APP_ID: com.taro.demo # Application Product Bundle Identifier
APP_NAME: Taro Demo # The Display Name of your app
VERSION_NUMBER: 1.0.0 # Application version number
BUILD_NUMBER: 1.0.0.0 # Application build number, used by release only.
TEAM_ID: XXXXXXXXXX # Team ID, is used when upgrading project
PROVISIONING_PROFILE_SPECIFIER: Product_profile # Provisioning profile name to use for code signing
CODE_SIGN_IDENTITY: iPhone Distribution # Code signing identity type (iPhone Developer, iPhone Distribution)
SIGNING_CERTIFICATE_P12_DATA: ${{secrets.RELEASE_SIGNING_CERTIFICATE_P12_DATA}}
SIGNING_CERTIFICATE_PASSWORD: ${{secrets.RELEASE_SIGNING_CERTIFICATE_PASSWORD}}
PROVISIONING_PROFILE_DATA: ${{secrets.RELEASE_PROVISIONING_PROFILE_DATA}}
APP_STORE_CONNECT_USERNAME: ${{secrets.APP_STORE_CONNECT_USERNAME}} # This secret should be set to the Apple ID of your developer account, used by release only.
APP_STORE_CONNECT_PASSWORD: ${{secrets.APP_STORE_CONNECT_PASSWORD}} # used by release only.values like ${{secrets.xxxxx}} are manually generated and store in your github encrypted secrets.
cat Certificates.p12 | base64 | pbcopy
encryption password of your Personal Information Exchange (.p12)
cat profile.mobileprovision | base64 | pbcopy
This secret should be set to an application-specific password for your Apple ID account. Follow these instructions to create an application-specific password.
Modify the following configuration items for package and publish your app.
.github/workflows/assemble_android_debug.yml .github/workflows/assemble_android_release.yml
env:
APP_ID: com.taro.demo # Application Product Bundle Identifier
APP_NAME: Taro Demo # The Display Name of your app
VERSION_NAME: 1.0.0 # version name
VERSION_CODE: 10 # version code
KEYSTORE_FILE: debug.keystore # key store file
KEYSTORE_PASSWORD: android # key store password
KEYSTORE_KEY_ALIAS: androiddebugkey # key store key alias
KEYSTORE_KEY_PASSWORD: android # key store key passwordFor the security of your app, please regenerate the .keystore file and store the password in your github encrypted secrets.
This project supports web and mini program, but it has not been fully tested.
yarn dev:h5see peaceiris/actions-gh-pages for more details.
yarn dev:weappWe use @tarojs/plugin-mini-ci to deploy mini programs. Modify the following configuration items for package and publish your wechat mini program.
env:
WEAPP_ID: ${{ secrets.WEAPP_ID }} # wechat mini program id
WEAPP_KEY: ${{ secrets.WEAPP_KEY }} # wechat mini program keyvalues like ${{secrets.xxxxx}} are manually generated and store in your github encrypted secrets.
cat private.$WEAPP_ID.key | base64 | pbcopy
The source code is customized for the Taro playground application and is for reference only. If you want to use it directly, please make the following changes.
- Use your own signature file.
- Customize your app id, app name, app launcher, etc.
- Remove the attention block in ios/Podfile.
- Change appName to
taroDemo, which used inAppRegistry.registerComponent(appName, () => App);. - Generate a QR code with content
taro://${ip}:${port}or shaking the phone and change bundle Location.
We sincerely hope that developers can provide valuable comments and suggestions, and developers can provide feedback on suggestions and problems by submitting PR or Issue.
If you have other questions, you can join the communication group for help.
Taro Playground source code is available under the Apache License V2.
Taro and its graphic trademarks are owned by Beijing Jingdong Century Trading Co., Ltd. and licensed to the Taro Playground project.
