Build Your Mobile Development Kit Client Using Cloud Build Service

This step is required only if you will be using Push notification in your Android MDK client. If not using the Push, proceed to next step.

1. Open the Firebase console, login with your Google account and click Create a new Firebase Project.

   

2. Provide a Project Name, click Continue.

   

3. Uncheck Enable Gemini in Firebase option and click Continue.

   

4. Uncheck Enable Google Analytics for this project option and click Create Project.

   

5. Once the project is ready, click Continue.

   

6. Click Add app and click Android icon to add Firebase to your Android app.

   

7. Provide a unique name to Android package name, click Register app.

   

8. Download google-services.json file, click Next.

   

9. In Add Firebase SDK step, click Next.

10. In the following step, click Next and then click Continue to console.

    

In order to implement Push Notifications, a paid Apple developer account is required. Students or other developers with a personal Apple ID for their team will not be able to use push notifications, because they will not have access to the Developer Portal to generate the required certificate.

To enable your app for push notifications, you need to carry out the following tasks:

• Obtain a certificate signing request
• Create a new development certificate .cer file
• Install the .cer file and create the .p12 file
• Register an iOS App ID
• Register your device
• Create a development provisioning profile

1. Obtain a certificate signing request

   In order to use the Apple Push Notification service, you need to create a CSR file.

   On your Mac, open the Keychain Access application, and navigate to Keychain Access > Certificate Assistant > Request a Certificate From a Certificate Authority…

   

   In the dialog, enter the email address which is associated with your Apple Developer account. Also, make sure you check the Request is saved to disk option.

   

   Click Continue.

   Choose a folder to store the certificate – it is good practice to store generated files in a separate folder for each project – and click Save.

   Once you see a dialog saying the certificate is saved successfully, click Done to finish.

   

2. Create a new development certificate .cer file

   Go to your Apple Developer Account and Click Certificates.

   

   Click + icon to create a Certificate for your app.

   

   Select Apple Development and click Continue.

   

   Click Choose File and browse to the downloaded Signing Request CSR file, click Continue.

   Apple will now create a .cer file for you which is issued by the Apple Worldwide Developer Relations Certification Authority.

   

   Click Download to download your certificate.

   

3. Install the .cer file and create the .p12 file

   In order to create a signing profile on SAP Mobile Services, you need to install the .cer file and create the needed .p12 file.

   A .p12 file is a encrypted container for the certificate and private key. This file is needed by Mobile Services for creating a signing profile.

   Locate your downloaded .cer file and double-click it in order to install the certificate.

   In case the Add Certificate dialog pops up make sure to choose Login from the dropdown and click Add.

   If the certificate is added correctly to the Keychain you should see it in the MyCertificates section, make sure you selected login as keychain.

   

   Select the certificate as well as the private key and right-click to export those 2 items.

   

   Make sure that in the dropdown Personal Information Exchange (.p12) is selected and click Save. You will be prompted to enter a password, click OK to export the files.

   

4. Register an iOS App ID

   Click + icon to register a unique Identifiers for your app.

   

   Select App IDs and click Continue.

   

   Provide a unique Bundle ID name, Description and click Continue.

   

   In the following screen, select option for Deployment Details and then click Continue.

   Confirm your App ID by clicking on Register.

5. Register your device

   Click + icon to register your iOS device.

   

   Provide Device Name & Device ID (UDID) and then click Continue.

   

6. Create a development provisioning profile

   Click + icon to create a development provisioning profile.

   

   Select iOS App Development to create a provisioning profile to install development apps on test devices and click Continue.

   

   Select an App ID from the dropdown list and click Continue.

   

   Select the required certificate to include in this provisioning profile and click Continue.

   

   Select the device to include in this provisioning profile and click Continue.

   

   Provide a unique name to the profile and click Generate.

   

   In next step, download the generated provisioning profile on your local machine.

   

1. Open the SAP Mobile Services admin UI and navigate to Settings | Cloud Build. Initialize the Cloud Build Settings if not done before.

2. You have an option to generate a new signing profile in the Mobile Services admin UI by providing mandatory info like Profile Name, Validity, Common Name (user name). Other information are optional.

   

   Or you have an option to to upload an Android Signing profile, if you already have one.

   

1. Open the SAP Mobile Services admin UI and navigate to Settings | Cloud Build. Initialise the Cloud Build Settings if not done before.

2. Click Upload to upload iOS Signing profile and provide below information:

   Property	Value
   Platforms	iOS
   Profile Name	provide a name of your choice
   Signing Certificate	Browse to .p12 certificate
   Private Key Passphrase	Enter the password that you chose while exporting .p12 certificate
   provisioning Profile	Browse to .mobileprovision file

   Click OK.

   

1. Navigate to Mobile Applications → Native/MDK → myapp.mdk.demo → Cloud Build.

   If you do not see Cloud Build feature in the Assigned Features list, click the + icon to add it.

2. Click Create Build Job to build your first build job.

   

3. In the Basic Information step, select mobile development kit Client from Client Type dropdown.

   

4. Provide required values and click Next.

   

   Bundle ID (iOS)/ Package Name (Android) is a unique app identifier used to sign mobile development kit clients. For iOS, make sure to provide the same bundle ID while registering an iOS App ID in step 1.

5. In the Platform step, provide a unique value to the URL Scheme.

   If you have a Firebase configuration for your client, browse to select the google-services.json file and click Next.

   

   Google Services JSON File: The Firebase Android configuration file associated with your app in your Firebase project.

   For Android builds: The packaging format to use for the build, including APK (Android Package Kit, the default) or AAB (Android App Bundle). Since Google requires applications uploaded to the Google Play Store be built in the AAB format, select this option if that is your plan. To install an AAB binary without using Google Play Store, you must download the AAB and use Google’s bundletool to extract an install-ready binary from the AAB and to install that binary. Refer to their documentation on bundletool for more details.

6. In the Multimedia step, you may upload an image to use for the app logo and click Next.

   

7. In the Build Options step, select respective Signing profile(s), set minimum platform version, select a supported SDK version and click Finish.

   

   The default version is always recommended (it will vary over time), but you can select an older SDK version.

8. Click Build to start the Build job.

   

   After few minutes, Build should be completed. You can select each cloud build history row to view its current state, install, and download binaries.

   

   You can find more details about packaging details in help documentation.

1. In Mobile Services admin UI, navigate to Mobile Applications → Native/MDK → myapp.mdk.demo → Cloud Build.

   If you do not see Cloud Build feature in the Assigned Features list, click the + icon to add it.

2. Click Create Build Job to build your first build job.

   

3. In the Basic Information step, select Customized mobile development kit Client from Client Type dropdown.

   

   The build includes functionality to run customized extensions, application resources, and onboarding, and to include demo mode in your application.

4. Browse to your compressed MDK project as previously created.

   

   Upon upload, Cloud Build service starts validating the ZIP file. If the ZIP file doesn’t conform to the .mdkproject structure, you may see build failures. Check the documentation for more details.

   Once validation is successful, you will notice the values like Device App Name, Device App Display Name, Device App Version, Device App Details, Bundle ID, and Encrypt Database have been auto-filled/selected. These values were provided in your MDKProject.json and BrandedSettings.json as part of your local .mdkproject.

   

   Click Next.

5. In the Platform step, URL Scheme has been retrieved from the MDKProject.json. Click Next.

   If you have a Firebase configuration for your client, browse to select the google-services.json file and click Next.

   

   Google Services JSON File: The Firebase Android configuration file associated with your app in your Firebase project. If the google-services.json is available in the uploaded ZIP file, you will see option Show Contents to view the contents of the JSON file. If it is not the right file, click Remove File and then you can upload a new google-services.json file to override it.

   For Android builds: The packaging format to use for the build, including APK (Android Package Kit, the default) or AAB (Android App Bundle). Since Google requires applications uploaded to the Google Play Store be built in the AAB format, select this option if that is your plan. To install an AAB binary without using Google Play Store, you must download the AAB and use Google’s bundletool to extract an install-ready binary from the AAB and to install that binary. Refer to their documentation on bundletool for more details.

6. In the Multimedia step, you may upload an image to use for the app logo and click Next.

   

7. In the Build Options step, select respective Signing profile(s), set minimum platform version, select a supported SDK version and click Finish.

   

   The default version is always recommended (it will vary over time), but you can select an older SDK version.

8. Click Build to start the Build job.

   

   After few minutes, Build should be completed. You can select each cloud build history row to view its current state, install, and download binaries.

   

   You can find more details about packaging details in help documentation.

You can install this new custom MDK client app either by scanning QR code from Android phone camera app (click Install) or download binary (APK) locally and install in your device via IDEs like Android Studio or via other means.

You can install this new custom MDK client app either by scanning QR code from iPhone phone camera app (click Install) or download binary (IPA) locally and install in your device via IDEs like Xcode or via other means.