Auto build and upload your project build to Firebase, PlayStore and AppStore.
Features:
- Auto build project based on env files
- Deploy builds to Firebase (CLI/API)
- Deploy builds to Google Play Store (API)
- Deploy builds to Apple Store (xcrun altool)
- Support --dart-define-from-file arg
Activate: dart pub global activate budinoh
Create a budinoh.yaml
file in project directory
budinoh:
<content>
With your builds
builds:
<name>:
apk: {} # Optional
appbundle: {} # Optional
ipa: # Optional
export_options: <path/ExportOptions.plist> # Optional
You can auto-distribute your app on firebase, google play console (google_store) and apple store
firebase_api_credentials: # Optional. Path to file or Json String
builds:
<name>:
<apk|ios>:
firebase_cli:
app_id: <firebase_app_id> # Required
groups: # Optional
- group-one
- group-two
<apk|ios>:
firebase_api:
credentials: # Optional. Path to file or Json String. If missing it use credentials in firebase_api_credentials
app_id: <firebase_app_id> # Required
groups: # Optional
- group-one
- group-two
appbundle:
google_store:
credentials: ./google_service_account.json # Optional. Path to file or Json String
package_name: <com.example> # Required
ios:
apple_store:
api_issuer: <APIISSUER> # Required
api_key_id: <APIKEYID> # Required
apiKey: '.' # Optional. Path to directory or api key content
Are you using an env? Budinoh will search the directory you tell it for an env file with this name '${prefixEnv}${buildKey}${suffixEnv}'.
env:
directory: '.' # Optional. Environments directory
prefix: <.config.> # Optional. Prefix env file name
suffix: <.json> # Optional. Suffix env file name
Set env: {}
to enable use of the env with the default parameters
- Run
dart pub global run budinoh
- See output in
<PROJECT_DIR>/build_output/<ENV_NAME>/<BUILD_FILE>
Run dart pub global run budinoh --help
final client = BuildClient();
client.buildApk(env: , args: );
client.buildAppBundle(env: , args: );
client.buildIpa(exportOptions: , env: , args: );
final client = DistributionClient();
/// Use the Firebase CLI
client.uploadToFirebaseByCli(buildFile, appId: , releaseNotes: ,groups: );
/// Use the Firebase Rest Api
client.uploadToFirebaseByApi(buildFile, credentials: , appId: , releaseNotes: ,groups: );
/// Use the 'xcrun altool --upload-app' command
client.uploadAppToAppleStore(buildFile, apiIssuer: , apiKeyId: , apiKey: );
/// Use the 'https://www.googleapis.com/auth/androidpublisher' Google REST Api
client.uploadToGoogleStore(buildFile, credentials: , packageName: );
- Open the Google Cloud Console and select your project.
- Click Create Service Account and enter service account details.
- Click Create and Continue.
- Add the Firebase App Distribution Admin role and click Done.
- Create a private JSON key and move the key to a location accessible to your build environment. Be sure to keep this file somewhere safe, because it grants administrator access to App Distribution in your Firebase project.
More Info at this link
- Open the Google Play Console
- Click Account Details, and note the Developer Account ID listed there
- Click Setup โ API access
- Click the Create new service account button
- Follow the Google Cloud Platform link in the dialog, which opens a new tab/window:
- Click the CREATE SERVICE ACCOUNT button at the top of the Google Cloud Platform Console
- Verify that you are on the correct Google Cloud Platform Project by looking for the Developer Account ID from earlier within the light gray text in the second input, preceding .iam.gserviceaccount.com. If not, open the picker in the top navigation bar, and find the one with the ID that contains it.
- Provide a Service account name and click Create
- Click Select a role, then find and select Service Account User, and proceed
- Click the Done button
- Click on the Actions vertical three-dot icon of the service account you just created
- Select Manage keys on the menu
- Click ADD KEY -> Create New Key
- Make sure JSON is selected as the Key type, and click CREATE
- Save the file on your computer when prompted and remember where it was saved to
- Return to the Google Play Console tab, and click DONE to close the dialog
- Click on Grant Access for the newly added service account at the bottom of the screen (you may need to click Refresh service accounts before it shows up)
- Choose the permissions you'd like this account to have. We recommend Admin (all permissions), but you may want to manually select all checkboxes and leave out some of the Releases permissions such as Release to production
- Click Invite user to finish
More Info at this link at Collect your Google credentials
paragraph.
- Create a new App Store Connect API Key in the Users page
- For more info, go to the App Store Connect API Docs
- Select the "Keys" tab
- Give your API Key an appropriate role for the task at hand. You can read more about roles in Permissions in App Store Connect
- Note the Issuer ID as you will need it for the configuration steps below
- Download the newly created API Key file (.p8)
- This file cannot be downloaded again after the page has been refreshed
More Info at this link at Creating an App Store Connect API Key
paragraph.
Build your app based on env. You can change the bundle_id or app name according to the env used. See documents for more information