Destinations

When your platform is setup Everyday Digital will preload destinations for your app. However you might need to setup additional destinations when customers would like their app published under their accounts. In these scenarios follow the guides below.

The Everyday App CLI uses a combination of delegated and API access. To simplify this process we have created a static developer account which is automatically assigned to destinations. This developer account is provided when setting up a new destination.

App Store & Google Play Destination details are stored encrypted and only temporarily. Once a build machine validates the destinations details are obfuscated on the platform.

Google Firebase

This process requires you to delegate access to Everyday Raven CLI and register the Firebase project details with Raven.

  • Delegate Access. Add the dedicated Everyday Raven CLI account as a user on your Firebase Project. The user must be an admin / owner role.

  • Create Firebase Destination. Log onto the platform and navigate to Raven, then Destinations. Select the plus icon and select Firebase.

  • Provide Project Settings. In Firebase, navigate to Project Settings and copy the Project Number & ID as well as the Web API Key into Raven.

  • Provide Cloud Messaging Settings. In Firebase, Navigate to cloud messaging and copy the Server Key and Web Push certificate Key Pair.

  • Save the destination. Firebase destinations are immediately ready for web app deployments as soon as they are created.

The Web API Key might not be available, if so navigate to Authentication on Firebase and select get started.

Apple App Store

This process requires you to setup API access between your App Store account and Raven. Once setup and validated the credentials are stored safely on the Build machine and obfuscated on the platform. Part of these steps are summarised from the official docs https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api.

Steps 1 - 3 must be done by the Apple Developer account holder.

  1. Delegate Access. Add the dedicated Everyday Raven CLI account as a user on App Store Connect. The user must be an admin role.

  2. Generate API Keys. In App Store Connect navigate to Users & Access then select the API Keys tab. Click generate key and follow the prompts.

  3. Download Key. Once the API Key is created download the key and store in a safe place.

  4. Create App Store Destination. Log onto the platform and navigate to Raven, then Destinations. Select the plus icon and select App Store.

  5. Provide Team Details. Enter your Team Name and Team ID, these details are available on App Store connect.

  6. Provide API Settings. Enter Issuer ID and Key ID, these IDs are found under Users & Access in the Keys section in App Store Connect.

  7. Provide Private Key. Open the downloaded key from Step 3 (in a notepad or text editor), inside will be a private key. Copy the contents and paste into the Private Key field.

  8. Validation. Before a new App Store destination can be used with an app, a build machine will need to first validate the destination settings. This allows a build machine to test details before storing the destination details. Once validated you will be notified that the destination can be used.

Google Play Store

This process requires you to setup a Service account on Google Cloud with your Google Play Console account.

Steps 1 - 7 must be done by the Google Play Console account holder.

  1. Delegate Access. Add the dedicated Everyday Raven CLI account as a user the Google Play Console. The user must be an admin role.

  2. Generate API access. In Google Play Console navigate to Setup then API Access.

  3. Create Service Account. Click Create Service Account, this will show a prompt. Click the link that says Go to the Google Cloud Platform. This will open Google Cloud Platform Service Accounts. In Service accounts click Create Service Account.

  4. Setup service account details. Give the account a name, option description and select create and continue. On the last step select Done

  5. Set service account role. Select the service account user as the role then click continue.

  6. Generate Keys. Select options then Manage Keys on the created service account. Select Add Key then Create New Key. Select JSON for the type then select Create. This will generate a JSON file with credentials to be used in Raven.

  7. Set service account permission. In Google Play Console, navigate to Setup then API Access. You should now see service account created. Select the Grant Access option and set permission as admin and leave app permission to all.

Private App Store & Google Play

Apple Business Manager (Private Distribution) If you would like to distribute an app privately to a single or group of organizations you will need manually configure on App Store Connect. This is done under Pricing and Availability under the heading App Distribution Methods.

https://help.apple.com/app-store-connect/#/dev275598f16

Managed Google Play (Private Distribution) If you would like to distribute an app privately to a single or group of organizations you will need manually configure on Google Play Console. This is done under Advanced Settings under the tab Managed Google Play.

https://support.google.com/googleplay/work/answer/6145139#zippy=%2Cpublish-to-your-own-organization

Other App Stores

If you need to distribute android apps to stores other than Google Play you can manually upload AAB files.

Where to find build files To distribute Android apps to other stores you will need to download the build file. View device testing guide to see where you can download these files.

Device Testing

Huawei App Gallery

Follow the Getting Started and Upload App Bundle guide for Hauwei App Gallery. You will need to request an upload key from Everyday Digital.

Getting Started https://developer.huawei.com/consumer/en/doc/distribution/app/agc-help-getstarted-0000001100316670

Upload App Bundle https://developer.huawei.com/consumer/en/doc/distribution/app/agc-help-releasebundle-0000001100316672

Manual Android App Distribution outside of Google Play

The Raven build and deployment process is based on Google Play guidelines, standards and dependencies. However, you may download the AAB (Android App Bundle) or APK (Android Application Kit) and distribute it through alternative means. In cases of external distribution, the following understanding is needed, and conditions apply:

  1. No Guarantee. We support Google Play and Managed Google Play distribution through the Google Play Console. If you want to use an alternative distribution, please be aware that we do not offer guarantees on compatibility outside of Google Play Console.

  2. Signing/Upload key. We can provide a once off signing/upload key. We encourage you to store this key securely. Lost keys, compromised keys, or the need to regenerate a key will incur additional costs at ED's Developer Rate.

  3. Additional Support. We can assist in distributing the Android app through alternative means for a quoted fee, but we offer no guarantee that the alternative means will ultimately work.

  4. Manual Updates. If an alternative distribution platform is used, you will be required to monitor and manually update/upload new versions of the AAB when/as they become available.

If you require a controlled distribution, we recommend using Managed Google Play instead of alternative distribution platforms.

LogoManaged Google Play Helpsupport.google.com

Deploying an APK (Android Application Package)

  1. Setup a deployment in Raven.

  2. Under Android, select any Release type except for Skip.

  3. Select APK for Android Package Type.

  4. Wait for the deployment to complete.

  5. Select Deploy

  6. From the Android builds list, select options or view task to download the APK file.

PreviousDeploy Native AppsNextApp Designer

Last updated