The workflow can be triggered manually by providing the version input. Firebase_distribution: This job renames the signed APK and uploads it to Firebase Distribution.Github_Release: This job renames the signed APK and creates a Github release.setup_and_build: This job sets up JDK and Node.js, caches gradle dependencies, installs dependencies, generates a signed APK, and uploads the signed APK as an artifact.As a React Native developer, you will be responsible for developing and implementing new features, maintaining existing codebase, and ensuring that our mobile applications are running smoothly. The GOOGLE_SERVICES_JSON file and ANDROID_SIGNING_KEY are encoded in base64 for security purposes. We are looking for an experienced React Native developer to join our team and help us build cross-platform mobile applications. version: The version for naming the APK file and creating tags in the release for GitHub.The following variable is required to be passed as an input to the workflow: In Workflow permissions section, check the Read and Write permissions option. To set up these permissions in the workflow, go to Settings > Actions > General. Click on New repository secret and add each secret key-value pair. To set up these secrets, go to your repository on GitHub, then go to Settings > Secrets and variables > Actions. ANDROID_FIREBASE_TOKEN: The Firebase API token.ANDROID_FIREBASE_APP_ID: The Firebase App ID.ANDROID_KEY_PASSWORD: The password of your keystore's alias.ANDROID_KEY_STORE_PASSWORD: The password of your keystore.
ANDROID_SIGNING_KEY: Base64 encoded string of your Android keystore.GOOGLE_SERVICES_JSON: Base64 encoded Google Services JSON used in app.The following secrets are required to be setup in your repository: It includes steps to set up JDK and Node.js, cache Gradle dependencies, and generate a signed APK. This workflow automates the build, signing, and distribution of an Android APK for React Native apps to both Github Releases and Firebase Distribution.
0 kommentar(er)
