tjy-taro-rn

特别注意 添加第三方库别特须知

-- 如功能需要添加第三方库，需要查询通过npmjs查询该库与项目版本的兼容性版本；

1. 系统版本，详见package.json文件，当前版本使用的是 taro-rn@4.0.7-canary.3,及相关的锁定版本的其他库;

   # 尽量锁定安装依赖版本号，避免安装最新版本导致项目启动问题, 如下
   npm install sass@1.0.0
   #避免类似安装，因为这样子安装的当前依赖的最新的稳定的版本，不一定当前适用项目需要，导致其他的依赖包循环依赖进行跟新导致项目启动问题
   #一定要查阅文档，避免导致项目循环依赖包版本与包内部的依赖版本不一致导致项目启动问题
   # yarn add sass
   

2. 安装新的依赖包后，重新清空缓存，查看是否导致项目启动问题

# 安装新的依赖包
npm install 包名

# 安装新的依赖包后，重新清空缓存，查看是否导致项目启动问题
npx react-native start --reset-cache

1. 总之，添加新的包之前一定要慎重，切记

Supported versions

1. taro: @tarojs/cli@^3.2.0
2. 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 |

Quick start

install react native library

install peerDependencies of @tarojs/taro-rn @tarojs/components-rn and @tarojs/router-rn, it will also run post-install. please modify and run upgradePeerdeps script when you change taro version.

run this script after the project is initialized.

yarn upgradePeerdeps

pod install

run this script when you add new react native library or update react native library version.

see pod-install for more information.

yarn podInstall

start ios app

yarn ios

start android app

yarn android

start bundler

yarn start

reset cache and start bundler

yarn start --reset-cache

more information

1. development process of taro react native
2. github address of the taro project
3. related articles of taro playground

Release

build ios bundle

yarn build:rn --platform ios

build Android bundle

yarn build:rn --platform android

release ios APP

see publishing-to-app-store for details.

release android apk

see signed-apk-android for details.

Github workflows

use github actions to build your apps. this template include basic github action config.

see .github/workflows for details.

events

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

ios

configuration

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.

SIGNING_CERTIFICATE_P12_DATA

cat Certificates.p12 | base64 | pbcopy

SIGNING_CERTIFICATE_PASSWORD

encryption password of your Personal Information Exchange (.p12)

PROVISIONING_PROFILE_DATA

cat profile.mobileprovision | base64 | pbcopy

APP_STORE_CONNECT_PASSWORD

This secret should be set to an application-specific password for your Apple ID account. Follow these instructions to create an application-specific password.

read more

1. deploy an ios app to testflight or the app store using github actions
2. encrypted-secrets
3. fastlane

android

configuration

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 password

For the security of your app, please regenerate the .keystore file and store the password in your github encrypted secrets.

build

yarn build:rn --platform android --reset-cache
cd android
# 清理缓存
./gradlew clean
# 构建Release版本
./gradlew assembleRelease
# 构建debug包
./gradlew assembleDebug

read more

1. app signing
2. encrypted-secrets

Web & Mini Program support

This project supports web and mini program, but it has not been fully tested.

start web server

yarn dev:h5

Github workflows of Web

see peaceiris/actions-gh-pages for more details.

start wechat mini program

yarn dev:weapp

Github workflows of Wechat Mini Program

configuration

We use @tarojs/plugin-mini-ci to deploy mini programs. Modify the following configuration items for package and publish your wechat mini program.

.github/workflows/assemble_weapp_release.yml

env:
  WEAPP_ID: ${{ secrets.WEAPP_ID }} # wechat mini program id
  WEAPP_KEY: ${{ secrets.WEAPP_KEY }} # wechat mini program key

values like ${{secrets.xxxxx}} are manually generated and store in your github encrypted secrets.

WEAPP_KEY

cat private.$WEAPP_ID.key | base64 | pbcopy

Attention

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.

1. Use your own signature file.
2. Customize your app id, app name, app launcher, etc.
3. Remove the attention block in ios/Podfile.

For React Native repo debugging

1. Change appName to taroDemo, which used in AppRegistry.registerComponent(appName, () => App);.
2. Generate a QR code with content taro://${ip}:${port} or shaking the phone and change bundle Location.